database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-01 14:21:49 +03:00
Code

Clarify description of our deviation from standard for temp tables,

Browse Source 
per suggestion from Mike Sykes.
This commit is contained in:
Tom Lane 2003-04-14 15:24:46 +00:00
parent 810e0b982b
commit 6d99dbb0c9
1 changed files with 25 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
doc/src/sgml/ref/create_table.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.63 2003/03/25 16:15:39 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.64 2003/04/14 15:24:46 tgl Exp $
PostgreSQL documentation PostgreSQL documentation
--> -->
@ -826,24 +826,32 @@ CREATE TABLE distributors (
<title>Temporary Tables</title> <title>Temporary Tables</title>
<para> <para>
In addition to the local temporary table, SQL92 also defines a Although the syntax of <literal>CREATE TEMPORARY TABLE</literal>
<literal>CREATE GLOBAL TEMPORARY TABLE</literal> statement. resembles that of SQL92, the effect is not the same. In the standard,
Global temporary tables are also visible to other sessions. temporary tables are associated with modules; a temporary table is created
just once and automatically exists (starting with empty contents) in every
session that uses the module.
<productname>PostgreSQL</productname> does not have modules, and
requires each session to issue its own <literal>CREATE TEMPORARY
TABLE</literal> command for each temporary table to be used.
</para> </para>
<para> <note>
For temporary tables, there is an optional <literal>ON COMMIT</literal> clause: <para>
<synopsis> The spec-mandated behavior of temporary tables is widely ignored.
CREATE { GLOBAL | LOCAL } TEMPORARY TABLE <replaceable class="parameter">table</replaceable> ( <replaceable class="parameter">...</replaceable> ) [ ON COMMIT { DELETE | PRESERVE } ROWS ] <productname>PostgreSQL</productname>'s behavior on this point is similar
</synopsis> to that of several other RDBMSs.
</para>
</note>
The <literal>ON COMMIT</literal> clause specifies whether or not <para>
the temporary table should be emptied of rows whenever The optional <literal>ON COMMIT</literal> clause for temporary tables
<command>COMMIT</command> is executed. If the <literal>ON also resembles SQL92, but has some differences.
COMMIT</> clause is omitted, SQL92 specifies that the default is If the <literal>ON COMMIT</> clause is omitted, SQL92 specifies that the
<literal>ON COMMIT DELETE ROWS</>. However, the behavior of default behavior is <literal>ON COMMIT DELETE ROWS</>. However, the
<productname>PostgreSQL</productname> is always like <literal>ON default behavior in <productname>PostgreSQL</productname> is
COMMIT PRESERVE ROWS</literal>. <literal>ON COMMIT PRESERVE ROWS</literal>. The <literal>ON COMMIT
DROP</literal> option does not exist in SQL92 at all.
</para> </para>
</refsect2> </refsect2>
@ -854,7 +862,7 @@ CREATE { GLOBAL | LOCAL } TEMPORARY TABLE <replaceable class="parameter">table</
The <literal>NULL</> <quote>constraint</quote> (actually a The <literal>NULL</> <quote>constraint</quote> (actually a
non-constraint) is a <productname>PostgreSQL</productname> non-constraint) is a <productname>PostgreSQL</productname>
extension to SQL92 that is included for compatibility with some extension to SQL92 that is included for compatibility with some
other RDBMS (and for symmetry with the <literal>NOT other RDBMSs (and for symmetry with the <literal>NOT
NULL</literal> constraint). Since it is the default for any NULL</literal> constraint). Since it is the default for any
column, its presence is simply noise. column, its presence is simply noise.
</para> </para>