diff options
Diffstat (limited to 'doc/src/sgml/ref')
| -rw-r--r-- | doc/src/sgml/ref/alter_foreign_table.sgml | 28 | ||||
| -rw-r--r-- | doc/src/sgml/ref/alter_table.sgml | 37 | ||||
| -rw-r--r-- | doc/src/sgml/ref/copy.sgml | 32 | ||||
| -rw-r--r-- | doc/src/sgml/ref/create_materialized_view.sgml | 5 | ||||
| -rw-r--r-- | doc/src/sgml/ref/create_table.sgml | 88 | ||||
| -rw-r--r-- | doc/src/sgml/ref/create_table_as.sgml | 35 | ||||
| -rw-r--r-- | doc/src/sgml/ref/pg_dump.sgml | 14 | ||||
| -rw-r--r-- | doc/src/sgml/ref/select_into.sgml | 7 |
8 files changed, 46 insertions, 200 deletions
diff --git a/doc/src/sgml/ref/alter_foreign_table.sgml b/doc/src/sgml/ref/alter_foreign_table.sgml index f266be0c37..b27eb6f2aa 100644 --- a/doc/src/sgml/ref/alter_foreign_table.sgml +++ b/doc/src/sgml/ref/alter_foreign_table.sgml @@ -50,7 +50,6 @@ ALTER FOREIGN TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceab ENABLE TRIGGER [ <replaceable class="parameter">trigger_name</replaceable> | ALL | USER ] ENABLE REPLICA TRIGGER <replaceable class="parameter">trigger_name</replaceable> ENABLE ALWAYS TRIGGER <replaceable class="parameter">trigger_name</replaceable> - SET WITH OIDS SET WITHOUT OIDS INHERIT <replaceable class="parameter">parent_table</replaceable> NO INHERIT <replaceable class="parameter">parent_table</replaceable> @@ -224,33 +223,12 @@ ALTER FOREIGN TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceab </varlistentry> <varlistentry> - <term><literal>SET WITH OIDS</literal></term> - <listitem> - <para> - This form adds an <literal>oid</literal> system column to the - table (see <xref linkend="ddl-system-columns"/>). - It does nothing if the table already has OIDs. - Unless the table's foreign-data wrapper supports OIDs, this column - will simply read as zeroes. - </para> - - <para> - Note that this is not equivalent to <literal>ADD COLUMN oid oid</literal>; - that would add a normal column that happened to be named - <literal>oid</literal>, not a system column. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><literal>SET WITHOUT OIDS</literal></term> <listitem> <para> - This form removes the <literal>oid</literal> system column from the - table. This is exactly equivalent to - <literal>DROP COLUMN oid RESTRICT</literal>, - except that it will not complain if there is already no - <literal>oid</literal> column. + Backward compatibility syntax for removing the <literal>oid</literal> + system column. As oid system columns cannot be added anymore, this never + has an effect. </para> </listitem> </varlistentry> diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index f13a6cd944..be1647937d 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -72,7 +72,6 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="parameter">name</replaceable> NO FORCE ROW LEVEL SECURITY CLUSTER ON <replaceable class="parameter">index_name</replaceable> SET WITHOUT CLUSTER - SET WITH OIDS SET WITHOUT OIDS SET TABLESPACE <replaceable class="parameter">new_tablespace</replaceable> SET { LOGGED | UNLOGGED } @@ -614,31 +613,12 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM </varlistentry> <varlistentry> - <term><literal>SET WITH OIDS</literal></term> - <listitem> - <para> - This form adds an <literal>oid</literal> system column to the - table (see <xref linkend="ddl-system-columns"/>). - It does nothing if the table already has OIDs. - </para> - - <para> - Note that this is not equivalent to <literal>ADD COLUMN oid oid</literal>; - that would add a normal column that happened to be named - <literal>oid</literal>, not a system column. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><literal>SET WITHOUT OIDS</literal></term> <listitem> <para> - This form removes the <literal>oid</literal> system column from the - table. This is exactly equivalent to - <literal>DROP COLUMN oid RESTRICT</literal>, - except that it will not complain if there is already no - <literal>oid</literal> column. + Backward compatibility syntax for removing the <literal>oid</literal> + system column. As oid system columns cannot be added anymore, this never + has an effect. </para> </listitem> </varlistentry> @@ -704,17 +684,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <varname>effective_io_concurrency</varname>, <varname>parallel_workers</varname>, <varname>seq_page_cost</varname>, <varname>random_page_cost</varname>, <varname>n_distinct</varname> and <varname>n_distinct_inherited</varname>. </para> - - <note> - <para> - While <command>CREATE TABLE</command> allows <literal>OIDS</literal> to be specified - in the <literal>WITH (<replaceable - class="parameter">storage_parameter</replaceable>)</literal> syntax, - <command>ALTER TABLE</command> does not treat <literal>OIDS</literal> as a - storage parameter. Instead use the <literal>SET WITH OIDS</literal> - and <literal>SET WITHOUT OIDS</literal> forms to change OID status. - </para> - </note> </listitem> </varlistentry> diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index 9f3c85bf7f..411941ed31 100644 --- a/doc/src/sgml/ref/copy.sgml +++ b/doc/src/sgml/ref/copy.sgml @@ -33,7 +33,6 @@ COPY { <replaceable class="parameter">table_name</replaceable> [ ( <replaceable <phrase>where <replaceable class="parameter">option</replaceable> can be one of:</phrase> FORMAT <replaceable class="parameter">format_name</replaceable> - OIDS [ <replaceable class="parameter">boolean</replaceable> ] FREEZE [ <replaceable class="parameter">boolean</replaceable> ] DELIMITER '<replaceable class="parameter">delimiter_character</replaceable>' NULL '<replaceable class="parameter">null_string</replaceable>' @@ -204,18 +203,6 @@ COPY { <replaceable class="parameter">table_name</replaceable> [ ( <replaceable </varlistentry> <varlistentry> - <term><literal>OIDS</literal></term> - <listitem> - <para> - Specifies copying the OID for each row. (An error is raised if - <literal>OIDS</literal> is specified for a table that does not - have OIDs, or in the case of copying a <replaceable - class="parameter">query</replaceable>.) - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><literal>FREEZE</literal></term> <listitem> <para> @@ -549,8 +536,6 @@ COPY <replaceable class="parameter">count</replaceable> place of columns that are null. <command>COPY FROM</command> will raise an error if any line of the input file contains more or fewer columns than are expected. - If <literal>OIDS</literal> is specified, the OID is read or written as the first column, - preceding the user data columns. </para> <para> @@ -824,7 +809,9 @@ only one flag bit is defined, and the rest must be zero: <term>Bit 16</term> <listitem> <para> - if 1, OIDs are included in the data; if 0, not + If 1, OIDs are included in the data; if 0, not. Oid system columns + are not supported in <productname>PostgreSQL</productname> + anymore, but the format still contains the indicator. </para> </listitem> </varlistentry> @@ -895,10 +882,9 @@ distribution). <para> If OIDs are included in the file, the OID field immediately follows the -field-count word. It is a normal field except that it's not included -in the field-count. In particular it has a length word — this will allow -handling of 4-byte vs. 8-byte OIDs without too much pain, and will allow -OIDs to be shown as null if that ever proves desirable. +field-count word. It is a normal field except that it's not included in the +field-count. Note that oid system columns are not supported in current +versions of <productname>PostgreSQL</productname>. </para> </refsect3> @@ -1001,7 +987,6 @@ COPY <replaceable class="parameter">table_name</replaceable> [ ( <replaceable cl FROM { '<replaceable class="parameter">filename</replaceable>' | STDIN } [ [ WITH ] [ BINARY ] - [ OIDS ] [ DELIMITER [ AS ] '<replaceable class="parameter">delimiter</replaceable>' ] [ NULL [ AS ] '<replaceable class="parameter">null string</replaceable>' ] [ CSV [ HEADER ] @@ -1013,7 +998,6 @@ COPY { <replaceable class="parameter">table_name</replaceable> [ ( <replaceable TO { '<replaceable class="parameter">filename</replaceable>' | STDOUT } [ [ WITH ] [ BINARY ] - [ OIDS ] [ DELIMITER [ AS ] '<replaceable class="parameter">delimiter</replaceable>' ] [ NULL [ AS ] '<replaceable class="parameter">null string</replaceable>' ] [ CSV [ HEADER ] @@ -1032,12 +1016,12 @@ COPY { <replaceable class="parameter">table_name</replaceable> [ ( <replaceable version 7.3 and is still supported: <synopsis> -COPY [ BINARY ] <replaceable class="parameter">table_name</replaceable> [ WITH OIDS ] +COPY [ BINARY ] <replaceable class="parameter">table_name</replaceable> FROM { '<replaceable class="parameter">filename</replaceable>' | STDIN } [ [USING] DELIMITERS '<replaceable class="parameter">delimiter</replaceable>' ] [ WITH NULL AS '<replaceable class="parameter">null string</replaceable>' ] -COPY [ BINARY ] <replaceable class="parameter">table_name</replaceable> [ WITH OIDS ] +COPY [ BINARY ] <replaceable class="parameter">table_name</replaceable> TO { '<replaceable class="parameter">filename</replaceable>' | STDOUT } [ [USING] DELIMITERS '<replaceable class="parameter">delimiter</replaceable>' ] [ WITH NULL AS '<replaceable class="parameter">null string</replaceable>' ] diff --git a/doc/src/sgml/ref/create_materialized_view.sgml b/doc/src/sgml/ref/create_materialized_view.sgml index eed4273c4b..7f31ab4d26 100644 --- a/doc/src/sgml/ref/create_materialized_view.sgml +++ b/doc/src/sgml/ref/create_materialized_view.sgml @@ -45,8 +45,7 @@ CREATE MATERIALIZED VIEW [ IF NOT EXISTS ] <replaceable>table_name</replaceable> <command>CREATE TABLE AS</command>, except that it also remembers the query used to initialize the view, so that it can be refreshed later upon demand. A materialized view has many of the same properties as a table, but there - is no support for temporary materialized views or automatic generation of - OIDs. + is no support for temporary materialized views. </para> </refsect1> @@ -95,7 +94,7 @@ CREATE MATERIALIZED VIEW [ IF NOT EXISTS ] <replaceable>table_name</replaceable> endterm="sql-createtable-storage-parameters-title"/> for more information. All parameters supported for <literal>CREATE TABLE</literal> are also supported for <literal>CREATE MATERIALIZED - VIEW</literal> with the exception of <literal>OIDS</literal>. + VIEW</literal>. See <xref linkend="sql-createtable"/> for more information. </para> </listitem> diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 4b9c8a7801..50d5597002 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -29,7 +29,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI ] ) [ INHERITS ( <replaceable>parent_table</replaceable> [, ... ] ) ] [ PARTITION BY { RANGE | LIST | HASH } ( { <replaceable class="parameter">column_name</replaceable> | ( <replaceable class="parameter">expression</replaceable> ) } [ COLLATE <replaceable class="parameter">collation</replaceable> ] [ <replaceable class="parameter">opclass</replaceable> ] [, ... ] ) ] -[ WITH ( <replaceable class="parameter">storage_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ] +[ WITH ( <replaceable class="parameter">storage_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] ) | WITHOUT OIDS ] [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ] [ TABLESPACE <replaceable class="parameter">tablespace_name</replaceable> ] @@ -40,7 +40,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI [, ... ] ) ] [ PARTITION BY { RANGE | LIST | HASH } ( { <replaceable class="parameter">column_name</replaceable> | ( <replaceable class="parameter">expression</replaceable> ) } [ COLLATE <replaceable class="parameter">collation</replaceable> ] [ <replaceable class="parameter">opclass</replaceable> ] [, ... ] ) ] -[ WITH ( <replaceable class="parameter">storage_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ] +[ WITH ( <replaceable class="parameter">storage_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] ) | WITHOUT OIDS ] [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ] [ TABLESPACE <replaceable class="parameter">tablespace_name</replaceable> ] @@ -51,7 +51,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI [, ... ] ) ] { FOR VALUES <replaceable class="parameter">partition_bound_spec</replaceable> | DEFAULT } [ PARTITION BY { RANGE | LIST | HASH } ( { <replaceable class="parameter">column_name</replaceable> | ( <replaceable class="parameter">expression</replaceable> ) } [ COLLATE <replaceable class="parameter">collation</replaceable> ] [ <replaceable class="parameter">opclass</replaceable> ] [, ... ] ) ] -[ WITH ( <replaceable class="parameter">storage_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ] +[ WITH ( <replaceable class="parameter">storage_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] ) | WITHOUT OIDS ] [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ] [ TABLESPACE <replaceable class="parameter">tablespace_name</replaceable> ] @@ -531,17 +531,13 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> A partition must have the same column names and types as the partitioned - table to which it belongs. If the parent is specified <literal>WITH - OIDS</literal> then all partitions must have OIDs; the parent's OID - column will be inherited by all partitions just like any other column. - Modifications to the column names or types of a partitioned table, or - the addition or removal of an OID column, will automatically propagate - to all partitions. <literal>CHECK</literal> constraints will be inherited - automatically by every partition, but an individual partition may specify - additional <literal>CHECK</literal> constraints; additional constraints with - the same name and condition as in the parent will be merged with the - parent constraint. Defaults may be specified separately for each - partition. + table to which it belongs. Modifications to the column names or types of + a partitioned table will automatically propagate to all partitions. + <literal>CHECK</literal> constraints will be inherited automatically by + every partition, but an individual partition may specify additional + <literal>CHECK</literal> constraints; additional constraints with the + same name and condition as in the parent will be merged with the parent + constraint. Defaults may be specified separately for each partition. </para> <para> @@ -1145,46 +1141,21 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM This clause specifies optional storage parameters for a table or index; see <xref linkend="sql-createtable-storage-parameters" endterm="sql-createtable-storage-parameters-title"/> for more - information. The <literal>WITH</literal> clause for a - table can also include <literal>OIDS=TRUE</literal> (or just <literal>OIDS</literal>) - to specify that rows of the new table - should have OIDs (object identifiers) assigned to them, or - <literal>OIDS=FALSE</literal> to specify that the rows should not have OIDs. - If <literal>OIDS</literal> is not specified, the default setting depends upon - the <xref linkend="guc-default-with-oids"/> configuration parameter. - (If the new table inherits from any tables that have OIDs, then - <literal>OIDS=TRUE</literal> is forced even if the command says - <literal>OIDS=FALSE</literal>.) - </para> - - <para> - If <literal>OIDS=FALSE</literal> is specified or implied, the new - table does not store OIDs and no OID will be assigned for a row inserted - into it. This is generally considered worthwhile, since it - will reduce OID consumption and thereby postpone the wraparound - of the 32-bit OID counter. Once the counter wraps around, OIDs - can no longer be assumed to be unique, which makes them - considerably less useful. In addition, excluding OIDs from a - table reduces the space required to store the table on disk by - 4 bytes per row (on most machines), slightly improving performance. - </para> - - <para> - To remove OIDs from a table after it has been created, use <xref - linkend="sql-altertable"/>. + information. For backward-compatibility the <literal>WITH</literal> + clause for a table can also include <literal>OIDS=FALSE</literal> to + specify that rows of the new table should not contain OIDs (object + identifiers), <literal>OIDS=TRUE</literal> is not supported anymore. </para> </listitem> </varlistentry> <varlistentry> - <term><literal>WITH OIDS</literal></term> <term><literal>WITHOUT OIDS</literal></term> <listitem> <para> - These are obsolescent syntaxes equivalent to <literal>WITH (OIDS)</literal> - and <literal>WITH (OIDS=FALSE)</literal>, respectively. If you wish to give - both an <literal>OIDS</literal> setting and storage parameters, you must use - the <literal>WITH ( ... )</literal> syntax; see above. + This is backward-compatible syntax for declaring a table + <literal>WITHOUT OIDS</literal>, creating a table <literal>WITH + OIDS</literal> is not supported anymore. </para> </listitem> </varlistentry> @@ -1528,29 +1499,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <refsect1 id="sql-createtable-notes"> <title>Notes</title> - - <para> - Using OIDs in new applications is not recommended: where - possible, using an identity column or other sequence - generator as the table's primary key is preferred. However, if - your application does make use of OIDs to identify specific - rows of a table, it is recommended to create a unique constraint - on the <structfield>oid</structfield> column of that table, to ensure that - OIDs in the table will indeed uniquely identify rows even after - counter wraparound. Avoid assuming that OIDs are unique across - tables; if you need a database-wide unique identifier, use the - combination of <structfield>tableoid</structfield> and row OID for the - purpose. - </para> - - <tip> - <para> - The use of <literal>OIDS=FALSE</literal> is not recommended - for tables with no primary key, since without either an OID or a - unique data key, it is difficult to identify specific rows. - </para> - </tip> - <para> <productname>PostgreSQL</productname> automatically creates an index for each unique constraint and primary key constraint to @@ -2089,7 +2037,7 @@ CREATE TABLE cities_partdef <para> The <literal>WITH</literal> clause is a <productname>PostgreSQL</productname> - extension; neither storage parameters nor OIDs are in the standard. + extension; storage parameters are not in the standard. </para> </refsect2> diff --git a/doc/src/sgml/ref/create_table_as.sgml b/doc/src/sgml/ref/create_table_as.sgml index 527138e787..679e8f521e 100644 --- a/doc/src/sgml/ref/create_table_as.sgml +++ b/doc/src/sgml/ref/create_table_as.sgml @@ -23,7 +23,7 @@ PostgreSQL documentation <synopsis> CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] <replaceable>table_name</replaceable> [ (<replaceable>column_name</replaceable> [, ...] ) ] - [ WITH ( <replaceable class="parameter">storage_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] ) | WITH OIDS | WITHOUT OIDS ] + [ WITH ( <replaceable class="parameter">storage_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] ) | WITHOUT OIDS ] [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ] [ TABLESPACE <replaceable class="parameter">tablespace_name</replaceable> ] AS <replaceable>query</replaceable> @@ -127,25 +127,22 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI This clause specifies optional storage parameters for the new table; see <xref linkend="sql-createtable-storage-parameters" endterm="sql-createtable-storage-parameters-title"/> for more - information. The <literal>WITH</literal> clause - can also include <literal>OIDS=TRUE</literal> (or just <literal>OIDS</literal>) - to specify that rows of the new table - should have OIDs (object identifiers) assigned to them, or - <literal>OIDS=FALSE</literal> to specify that the rows should not have OIDs. - See <xref linkend="sql-createtable"/> for more information. + information. For backward-compatibility the <literal>WITH</literal> + clause for a table can also include <literal>OIDS=FALSE</literal> to + specify that rows of the new table should contain no OIDs (object + identifiers), <literal>OIDS=TRUE</literal> is not supported anymore. + OIDs. </para> </listitem> </varlistentry> <varlistentry> - <term><literal>WITH OIDS</literal></term> <term><literal>WITHOUT OIDS</literal></term> <listitem> <para> - These are obsolescent syntaxes equivalent to <literal>WITH (OIDS)</literal> - and <literal>WITH (OIDS=FALSE)</literal>, respectively. If you wish to give - both an <literal>OIDS</literal> setting and storage parameters, you must use - the <literal>WITH ( ... )</literal> syntax; see above. + This is backward-compatible syntax for declaring a table + <literal>WITHOUT OIDS</literal>, creating a table <literal>WITH + OIDS</literal> is not supported anymore. </para> </listitem> </varlistentry> @@ -245,14 +242,6 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI TABLE AS</command> offers a superset of the functionality offered by <command>SELECT INTO</command>. </para> - - <para> - The <command>CREATE TABLE AS</command> command allows the user to - explicitly specify whether OIDs should be included. If the - presence of OIDs is not explicitly specified, - the <xref linkend="guc-default-with-oids"/> configuration variable is - used. - </para> </refsect1> <refsect1> @@ -281,12 +270,12 @@ CREATE TABLE films2 AS <para> Create a new temporary table <literal>films_recent</literal>, consisting of only recent entries from the table <literal>films</literal>, using a - prepared statement. The new table has OIDs and will be dropped at commit: + prepared statement. The new table will be dropped at commit: <programlisting> PREPARE recentfilms(date) AS SELECT * FROM films WHERE date_prod > $1; -CREATE TEMP TABLE films_recent WITH (OIDS) ON COMMIT DROP AS +CREATE TEMP TABLE films_recent ON COMMIT DROP AS EXECUTE recentfilms('2002-01-01'); </programlisting></para> </refsect1> @@ -325,7 +314,7 @@ CREATE TEMP TABLE films_recent WITH (OIDS) ON COMMIT DROP AS <listitem> <para> The <literal>WITH</literal> clause is a <productname>PostgreSQL</productname> - extension; neither storage parameters nor OIDs are in the standard. + extension; storage parameters are not in the standard. </para> </listitem> diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index b5fa4fb85c..2015410a42 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -439,20 +439,6 @@ PostgreSQL documentation </varlistentry> <varlistentry> - <term><option>-o</option></term> - <term><option>--oids</option></term> - <listitem> - <para> - Dump object identifiers (<acronym>OID</acronym>s) as part of the - data for every table. Use this option if your application references - the <acronym>OID</acronym> - columns in some way (e.g., in a foreign key constraint). - Otherwise, this option should not be used. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><option>-O</option></term> <term><option>--no-owner</option></term> <listitem> diff --git a/doc/src/sgml/ref/select_into.sgml b/doc/src/sgml/ref/select_into.sgml index 6c1a25f5ed..462e372381 100644 --- a/doc/src/sgml/ref/select_into.sgml +++ b/doc/src/sgml/ref/select_into.sgml @@ -104,13 +104,6 @@ SELECT [ ALL | DISTINCT [ ON ( <replaceable class="parameter">expression</replac <command>CREATE TABLE AS</command> offers a superset of the functionality provided by <command>SELECT INTO</command>. </para> - - <para> - To add OIDs to the table created by <command>SELECT INTO</command>, - enable the <xref linkend="guc-default-with-oids"/> configuration - variable. Alternatively, <command>CREATE TABLE AS</command> can be - used with the <literal>WITH OIDS</literal> clause. - </para> </refsect1> <refsect1> |