1999-07-22 17:09:15 +02:00
|
|
|
<!--
|
2010-09-20 22:08:53 +02:00
|
|
|
doc/src/sgml/ref/create_table_as.sgml
|
2001-12-08 04:24:40 +01:00
|
|
|
PostgreSQL documentation
|
1999-07-22 17:09:15 +02:00
|
|
|
-->
|
|
|
|
|
2017-10-20 03:16:39 +02:00
|
|
|
<refentry id="sql-createtableas">
|
2014-02-24 03:25:35 +01:00
|
|
|
<indexterm zone="sql-createtableas">
|
|
|
|
<primary>CREATE TABLE AS</primary>
|
|
|
|
</indexterm>
|
|
|
|
|
1999-06-14 09:37:05 +02:00
|
|
|
<refmeta>
|
2010-04-03 09:23:02 +02:00
|
|
|
<refentrytitle>CREATE TABLE AS</refentrytitle>
|
2008-11-14 11:22:48 +01:00
|
|
|
<manvolnum>7</manvolnum>
|
1999-06-14 09:37:05 +02:00
|
|
|
<refmiscinfo>SQL - Language Statements</refmiscinfo>
|
|
|
|
</refmeta>
|
2001-10-22 20:14:47 +02:00
|
|
|
|
1999-06-14 09:37:05 +02:00
|
|
|
<refnamediv>
|
2001-10-22 20:14:47 +02:00
|
|
|
<refname>CREATE TABLE AS</refname>
|
2004-08-24 02:06:51 +02:00
|
|
|
<refpurpose>define a new table from the results of a query</refpurpose>
|
1999-06-14 09:37:05 +02:00
|
|
|
</refnamediv>
|
2001-10-22 20:14:47 +02:00
|
|
|
|
1999-06-14 09:37:05 +02:00
|
|
|
<refsynopsisdiv>
|
2001-10-22 20:14:47 +02:00
|
|
|
<synopsis>
|
2014-12-13 19:56:09 +01:00
|
|
|
CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] <replaceable>table_name</replaceable>
|
2006-02-19 01:04:28 +01:00
|
|
|
[ (<replaceable>column_name</replaceable> [, ...] ) ]
|
2019-04-04 02:37:00 +02:00
|
|
|
[ USING <replaceable class="parameter">method</replaceable> ]
|
Remove WITH OIDS support, change oid catalog column visibility.
Previously tables declared WITH OIDS, including a significant fraction
of the catalog tables, stored the oid column not as a normal column,
but as part of the tuple header.
This special column was not shown by default, which was somewhat odd,
as it's often (consider e.g. pg_class.oid) one of the more important
parts of a row. Neither pg_dump nor COPY included the contents of the
oid column by default.
The fact that the oid column was not an ordinary column necessitated a
significant amount of special case code to support oid columns. That
already was painful for the existing, but upcoming work aiming to make
table storage pluggable, would have required expanding and duplicating
that "specialness" significantly.
WITH OIDS has been deprecated since 2005 (commit ff02d0a05280e0).
Remove it.
Removing includes:
- CREATE TABLE and ALTER TABLE syntax for declaring the table to be
WITH OIDS has been removed (WITH (oids[ = true]) will error out)
- pg_dump does not support dumping tables declared WITH OIDS and will
issue a warning when dumping one (and ignore the oid column).
- restoring an pg_dump archive with pg_restore will warn when
restoring a table with oid contents (and ignore the oid column)
- COPY will refuse to load binary dump that includes oids.
- pg_upgrade will error out when encountering tables declared WITH
OIDS, they have to be altered to remove the oid column first.
- Functionality to access the oid of the last inserted row (like
plpgsql's RESULT_OID, spi's SPI_lastoid, ...) has been removed.
The syntax for declaring a table WITHOUT OIDS (or WITH (oids = false)
for CREATE TABLE) is still supported. While that requires a bit of
support code, it seems unnecessary to break applications / dumps that
do not use oids, and are explicit about not using them.
The biggest user of WITH OID columns was postgres' catalog. This
commit changes all 'magic' oid columns to be columns that are normally
declared and stored. To reduce unnecessary query breakage all the
newly added columns are still named 'oid', even if a table's column
naming scheme would indicate 'reloid' or such. This obviously
requires adapting a lot code, mostly replacing oid access via
HeapTupleGetOid() with access to the underlying Form_pg_*->oid column.
The bootstrap process now assigns oids for all oid columns in
genbki.pl that do not have an explicit value (starting at the largest
oid previously used), only oids assigned later by oids will be above
FirstBootstrapObjectId. As the oid column now is a normal column the
special bootstrap syntax for oids has been removed.
Oids are not automatically assigned during insertion anymore, all
backend code explicitly assigns oids with GetNewOidWithIndex(). For
the rare case that insertions into the catalog via SQL are called for
the new pg_nextoid() function can be used (which only works on catalog
tables).
The fact that oid columns on system tables are now normal columns
means that they will be included in the set of columns expanded
by * (i.e. SELECT * FROM pg_class will now include the table's oid,
previously it did not). It'd not technically be hard to hide oid
column by default, but that'd mean confusing behavior would either
have to be carried forward forever, or it'd cause breakage down the
line.
While it's not unlikely that further adjustments are needed, the
scope/invasiveness of the patch makes it worthwhile to get merge this
now. It's painful to maintain externally, too complicated to commit
after the code code freeze, and a dependency of a number of other
patches.
Catversion bump, for obvious reasons.
Author: Andres Freund, with contributions by John Naylor
Discussion: https://postgr.es/m/20180930034810.ywp2c7awz7opzcfr@alap3.anarazel.de
2018-11-21 00:36:57 +01:00
|
|
|
[ WITH ( <replaceable class="parameter">storage_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] ) | WITHOUT OIDS ]
|
2006-02-19 01:04:28 +01:00
|
|
|
[ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
|
2017-10-09 04:00:57 +02:00
|
|
|
[ TABLESPACE <replaceable class="parameter">tablespace_name</replaceable> ]
|
2001-10-22 20:14:47 +02:00
|
|
|
AS <replaceable>query</replaceable>
|
2008-10-28 15:09:45 +01:00
|
|
|
[ WITH [ NO ] DATA ]
|
2003-04-22 12:08:08 +02:00
|
|
|
</synopsis>
|
1999-06-14 09:37:05 +02:00
|
|
|
</refsynopsisdiv>
|
2010-11-23 21:27:50 +01:00
|
|
|
|
1999-06-14 09:37:05 +02:00
|
|
|
<refsect1>
|
2003-04-22 12:08:08 +02:00
|
|
|
<title>Description</title>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<para>
|
2001-03-20 21:54:41 +01:00
|
|
|
<command>CREATE TABLE AS</command> creates a table and fills it
|
2006-09-18 21:54:01 +02:00
|
|
|
with data computed by a <command>SELECT</command> command.
|
|
|
|
The table columns have the
|
2003-07-01 02:04:31 +02:00
|
|
|
names and data types associated with the output columns of the
|
|
|
|
<command>SELECT</command> (except that you can override the column
|
|
|
|
names by giving an explicit list of new column names).
|
2001-10-22 20:14:47 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
<command>CREATE TABLE AS</command> bears some resemblance to
|
|
|
|
creating a view, but it is really quite different: it creates a new
|
|
|
|
table and evaluates the query just once to fill the new table
|
|
|
|
initially. The new table will not track subsequent changes to the
|
2002-04-23 04:07:16 +02:00
|
|
|
source tables of the query. In contrast, a view re-evaluates its
|
|
|
|
defining <command>SELECT</command> statement whenever it is
|
2001-10-22 20:14:47 +02:00
|
|
|
queried.
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Parameters</title>
|
2003-12-01 23:08:02 +01:00
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>GLOBAL</literal> or <literal>LOCAL</literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2012-06-13 23:48:42 +02:00
|
|
|
Ignored for compatibility. Use of these keywords is deprecated;
|
2017-11-23 15:39:47 +01:00
|
|
|
refer to <xref linkend="sql-createtable"/> for details.
|
2003-12-01 23:08:02 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
|
2001-10-22 20:14:47 +02:00
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><literal>TEMPORARY</literal> or <literal>TEMP</literal></term>
|
2001-10-22 20:14:47 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
If specified, the table is created as a temporary table.
|
2017-11-23 15:39:47 +01:00
|
|
|
Refer to <xref linkend="sql-createtable"/> for details.
|
2001-10-22 20:14:47 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2010-12-29 12:48:53 +01:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><literal>UNLOGGED</literal></term>
|
2010-12-29 12:48:53 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
If specified, the table is created as an unlogged table.
|
2017-11-23 15:39:47 +01:00
|
|
|
Refer to <xref linkend="sql-createtable"/> for details.
|
2010-12-29 12:48:53 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2014-12-13 19:56:09 +01:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><literal>IF NOT EXISTS</literal></term>
|
2014-12-13 19:56:09 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Do not throw an error if a relation with the same name already exists.
|
2017-11-23 15:39:47 +01:00
|
|
|
A notice is issued in this case. Refer to <xref linkend="sql-createtable"/>
|
2014-12-13 19:56:09 +01:00
|
|
|
for details.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-10-22 20:14:47 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><replaceable>table_name</replaceable></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2002-04-23 04:07:16 +02:00
|
|
|
The name (optionally schema-qualified) of the table to be created.
|
2001-10-22 20:14:47 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><replaceable>column_name</replaceable></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-04-22 12:08:08 +02:00
|
|
|
The name of a column in the new table. If column names are not
|
2011-11-25 05:21:06 +01:00
|
|
|
provided, they are taken from the output column names of the query.
|
2001-10-22 20:14:47 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2019-04-04 02:37:00 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><literal>USING <replaceable class="parameter">method</replaceable></literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
This optional clause specifies the table access method to use to store
|
|
|
|
the contents for the new table; the method needs be an access method of
|
|
|
|
type <literal>TABLE</literal>. See <xref linkend="tableam"/> for more
|
|
|
|
information. If this option is not specified, the default table access
|
2019-05-08 11:14:14 +02:00
|
|
|
method is chosen for the new table. See <xref
|
2019-04-04 02:37:00 +02:00
|
|
|
linkend="guc-default-table-access-method"/> for more information.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2004-01-11 00:28:45 +01:00
|
|
|
<varlistentry>
|
2017-10-09 04:00:57 +02:00
|
|
|
<term><literal>WITH ( <replaceable class="parameter">storage_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] )</literal></term>
|
2006-07-04 20:07:24 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
This clause specifies optional storage parameters for the new table;
|
|
|
|
see <xref linkend="sql-createtable-storage-parameters"
|
2017-11-23 15:39:47 +01:00
|
|
|
endterm="sql-createtable-storage-parameters-title"/> for more
|
Remove WITH OIDS support, change oid catalog column visibility.
Previously tables declared WITH OIDS, including a significant fraction
of the catalog tables, stored the oid column not as a normal column,
but as part of the tuple header.
This special column was not shown by default, which was somewhat odd,
as it's often (consider e.g. pg_class.oid) one of the more important
parts of a row. Neither pg_dump nor COPY included the contents of the
oid column by default.
The fact that the oid column was not an ordinary column necessitated a
significant amount of special case code to support oid columns. That
already was painful for the existing, but upcoming work aiming to make
table storage pluggable, would have required expanding and duplicating
that "specialness" significantly.
WITH OIDS has been deprecated since 2005 (commit ff02d0a05280e0).
Remove it.
Removing includes:
- CREATE TABLE and ALTER TABLE syntax for declaring the table to be
WITH OIDS has been removed (WITH (oids[ = true]) will error out)
- pg_dump does not support dumping tables declared WITH OIDS and will
issue a warning when dumping one (and ignore the oid column).
- restoring an pg_dump archive with pg_restore will warn when
restoring a table with oid contents (and ignore the oid column)
- COPY will refuse to load binary dump that includes oids.
- pg_upgrade will error out when encountering tables declared WITH
OIDS, they have to be altered to remove the oid column first.
- Functionality to access the oid of the last inserted row (like
plpgsql's RESULT_OID, spi's SPI_lastoid, ...) has been removed.
The syntax for declaring a table WITHOUT OIDS (or WITH (oids = false)
for CREATE TABLE) is still supported. While that requires a bit of
support code, it seems unnecessary to break applications / dumps that
do not use oids, and are explicit about not using them.
The biggest user of WITH OID columns was postgres' catalog. This
commit changes all 'magic' oid columns to be columns that are normally
declared and stored. To reduce unnecessary query breakage all the
newly added columns are still named 'oid', even if a table's column
naming scheme would indicate 'reloid' or such. This obviously
requires adapting a lot code, mostly replacing oid access via
HeapTupleGetOid() with access to the underlying Form_pg_*->oid column.
The bootstrap process now assigns oids for all oid columns in
genbki.pl that do not have an explicit value (starting at the largest
oid previously used), only oids assigned later by oids will be above
FirstBootstrapObjectId. As the oid column now is a normal column the
special bootstrap syntax for oids has been removed.
Oids are not automatically assigned during insertion anymore, all
backend code explicitly assigns oids with GetNewOidWithIndex(). For
the rare case that insertions into the catalog via SQL are called for
the new pg_nextoid() function can be used (which only works on catalog
tables).
The fact that oid columns on system tables are now normal columns
means that they will be included in the set of columns expanded
by * (i.e. SELECT * FROM pg_class will now include the table's oid,
previously it did not). It'd not technically be hard to hide oid
column by default, but that'd mean confusing behavior would either
have to be carried forward forever, or it'd cause breakage down the
line.
While it's not unlikely that further adjustments are needed, the
scope/invasiveness of the patch makes it worthwhile to get merge this
now. It's painful to maintain externally, too complicated to commit
after the code code freeze, and a dependency of a number of other
patches.
Catversion bump, for obvious reasons.
Author: Andres Freund, with contributions by John Naylor
Discussion: https://postgr.es/m/20180930034810.ywp2c7awz7opzcfr@alap3.anarazel.de
2018-11-21 00:36:57 +01:00
|
|
|
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.
|
2006-07-04 20:07:24 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
2004-01-11 00:28:45 +01:00
|
|
|
</varlistentry>
|
|
|
|
|
2006-07-02 04:23:23 +02:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><literal>WITHOUT OIDS</literal></term>
|
2006-07-02 04:23:23 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
Remove WITH OIDS support, change oid catalog column visibility.
Previously tables declared WITH OIDS, including a significant fraction
of the catalog tables, stored the oid column not as a normal column,
but as part of the tuple header.
This special column was not shown by default, which was somewhat odd,
as it's often (consider e.g. pg_class.oid) one of the more important
parts of a row. Neither pg_dump nor COPY included the contents of the
oid column by default.
The fact that the oid column was not an ordinary column necessitated a
significant amount of special case code to support oid columns. That
already was painful for the existing, but upcoming work aiming to make
table storage pluggable, would have required expanding and duplicating
that "specialness" significantly.
WITH OIDS has been deprecated since 2005 (commit ff02d0a05280e0).
Remove it.
Removing includes:
- CREATE TABLE and ALTER TABLE syntax for declaring the table to be
WITH OIDS has been removed (WITH (oids[ = true]) will error out)
- pg_dump does not support dumping tables declared WITH OIDS and will
issue a warning when dumping one (and ignore the oid column).
- restoring an pg_dump archive with pg_restore will warn when
restoring a table with oid contents (and ignore the oid column)
- COPY will refuse to load binary dump that includes oids.
- pg_upgrade will error out when encountering tables declared WITH
OIDS, they have to be altered to remove the oid column first.
- Functionality to access the oid of the last inserted row (like
plpgsql's RESULT_OID, spi's SPI_lastoid, ...) has been removed.
The syntax for declaring a table WITHOUT OIDS (or WITH (oids = false)
for CREATE TABLE) is still supported. While that requires a bit of
support code, it seems unnecessary to break applications / dumps that
do not use oids, and are explicit about not using them.
The biggest user of WITH OID columns was postgres' catalog. This
commit changes all 'magic' oid columns to be columns that are normally
declared and stored. To reduce unnecessary query breakage all the
newly added columns are still named 'oid', even if a table's column
naming scheme would indicate 'reloid' or such. This obviously
requires adapting a lot code, mostly replacing oid access via
HeapTupleGetOid() with access to the underlying Form_pg_*->oid column.
The bootstrap process now assigns oids for all oid columns in
genbki.pl that do not have an explicit value (starting at the largest
oid previously used), only oids assigned later by oids will be above
FirstBootstrapObjectId. As the oid column now is a normal column the
special bootstrap syntax for oids has been removed.
Oids are not automatically assigned during insertion anymore, all
backend code explicitly assigns oids with GetNewOidWithIndex(). For
the rare case that insertions into the catalog via SQL are called for
the new pg_nextoid() function can be used (which only works on catalog
tables).
The fact that oid columns on system tables are now normal columns
means that they will be included in the set of columns expanded
by * (i.e. SELECT * FROM pg_class will now include the table's oid,
previously it did not). It'd not technically be hard to hide oid
column by default, but that'd mean confusing behavior would either
have to be carried forward forever, or it'd cause breakage down the
line.
While it's not unlikely that further adjustments are needed, the
scope/invasiveness of the patch makes it worthwhile to get merge this
now. It's painful to maintain externally, too complicated to commit
after the code code freeze, and a dependency of a number of other
patches.
Catversion bump, for obvious reasons.
Author: Andres Freund, with contributions by John Naylor
Discussion: https://postgr.es/m/20180930034810.ywp2c7awz7opzcfr@alap3.anarazel.de
2018-11-21 00:36:57 +01:00
|
|
|
This is backward-compatible syntax for declaring a table
|
|
|
|
<literal>WITHOUT OIDS</literal>, creating a table <literal>WITH
|
|
|
|
OIDS</literal> is not supported anymore.
|
2006-07-02 04:23:23 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2006-02-19 01:04:28 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><literal>ON COMMIT</literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The behavior of temporary tables at the end of a transaction
|
|
|
|
block can be controlled using <literal>ON COMMIT</literal>.
|
|
|
|
The three options are:
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>PRESERVE ROWS</literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
No special action is taken at the ends of transactions.
|
|
|
|
This is the default behavior.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>DELETE ROWS</literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
All rows in the temporary table will be deleted at the end
|
|
|
|
of each transaction block. Essentially, an automatic <xref
|
2017-11-23 15:39:47 +01:00
|
|
|
linkend="sql-truncate"/> is done
|
2006-02-19 01:04:28 +01:00
|
|
|
at each commit.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>DROP</literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The temporary table will be dropped at the end of the current
|
|
|
|
transaction block.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2011-08-07 09:49:45 +02:00
|
|
|
</variablelist></para>
|
2006-02-19 01:04:28 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2017-10-09 04:00:57 +02:00
|
|
|
<term><literal>TABLESPACE <replaceable class="parameter">tablespace_name</replaceable></literal></term>
|
2006-02-19 01:04:28 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2017-10-09 04:00:57 +02:00
|
|
|
The <replaceable class="parameter">tablespace_name</replaceable> is the name
|
2006-02-19 01:04:28 +01:00
|
|
|
of the tablespace in which the new table is to be created.
|
|
|
|
If not specified,
|
2017-11-23 15:39:47 +01:00
|
|
|
<xref linkend="guc-default-tablespace"/> is consulted, or
|
|
|
|
<xref linkend="guc-temp-tablespaces"/> if the table is temporary.
|
2006-02-19 01:04:28 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-10-22 20:14:47 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><replaceable>query</replaceable></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2017-11-23 15:39:47 +01:00
|
|
|
A <xref linkend="sql-select"/>, <link
|
|
|
|
linkend="sql-table">TABLE</link>, or <xref linkend="sql-values"/>
|
|
|
|
command, or an <xref linkend="sql-execute"/> command that runs a
|
2017-10-09 03:44:17 +02:00
|
|
|
prepared <command>SELECT</command>, <command>TABLE</command>, or
|
|
|
|
<command>VALUES</command> query.
|
2001-10-22 20:14:47 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2008-10-28 15:09:45 +01:00
|
|
|
|
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><literal>WITH [ NO ] DATA</literal></term>
|
2008-10-28 15:09:45 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
This clause specifies whether or not the data produced by the query
|
|
|
|
should be copied into the new table. If not, only the table structure
|
|
|
|
is copied. The default is to copy the data.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-10-22 20:14:47 +02:00
|
|
|
</variablelist>
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Notes</title>
|
|
|
|
|
|
|
|
<para>
|
2003-12-01 23:08:02 +01:00
|
|
|
This command is functionally similar to <xref
|
2017-11-23 15:39:47 +01:00
|
|
|
linkend="sql-selectinto"/>, but it is
|
2003-12-01 23:08:02 +01:00
|
|
|
preferred since it is less likely to be confused with other uses of
|
2017-10-09 03:44:17 +02:00
|
|
|
the <command>SELECT INTO</command> syntax. Furthermore, <command>CREATE
|
2004-12-13 19:05:10 +01:00
|
|
|
TABLE AS</command> offers a superset of the functionality offered
|
2004-01-11 00:28:45 +01:00
|
|
|
by <command>SELECT INTO</command>.
|
2003-12-01 23:08:02 +01:00
|
|
|
</para>
|
2001-10-22 20:14:47 +02:00
|
|
|
</refsect1>
|
|
|
|
|
2005-01-09 06:57:45 +01:00
|
|
|
<refsect1>
|
|
|
|
<title>Examples</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Create a new table <literal>films_recent</literal> consisting of only
|
|
|
|
recent entries from the table <literal>films</literal>:
|
|
|
|
|
|
|
|
<programlisting>
|
|
|
|
CREATE TABLE films_recent AS
|
|
|
|
SELECT * FROM films WHERE date_prod >= '2002-01-01';
|
2006-02-19 01:04:28 +01:00
|
|
|
</programlisting>
|
|
|
|
</para>
|
|
|
|
|
2008-11-20 15:04:46 +01:00
|
|
|
<para>
|
|
|
|
To copy a table completely, the short form using
|
|
|
|
the <literal>TABLE</literal> command can also be used:
|
|
|
|
|
|
|
|
<programlisting>
|
|
|
|
CREATE TABLE films2 AS
|
|
|
|
TABLE films;
|
|
|
|
</programlisting>
|
|
|
|
</para>
|
|
|
|
|
2006-02-19 01:04:28 +01:00
|
|
|
<para>
|
2006-07-04 20:07:24 +02:00
|
|
|
Create a new temporary table <literal>films_recent</literal>, consisting of
|
|
|
|
only recent entries from the table <literal>films</literal>, using a
|
Remove WITH OIDS support, change oid catalog column visibility.
Previously tables declared WITH OIDS, including a significant fraction
of the catalog tables, stored the oid column not as a normal column,
but as part of the tuple header.
This special column was not shown by default, which was somewhat odd,
as it's often (consider e.g. pg_class.oid) one of the more important
parts of a row. Neither pg_dump nor COPY included the contents of the
oid column by default.
The fact that the oid column was not an ordinary column necessitated a
significant amount of special case code to support oid columns. That
already was painful for the existing, but upcoming work aiming to make
table storage pluggable, would have required expanding and duplicating
that "specialness" significantly.
WITH OIDS has been deprecated since 2005 (commit ff02d0a05280e0).
Remove it.
Removing includes:
- CREATE TABLE and ALTER TABLE syntax for declaring the table to be
WITH OIDS has been removed (WITH (oids[ = true]) will error out)
- pg_dump does not support dumping tables declared WITH OIDS and will
issue a warning when dumping one (and ignore the oid column).
- restoring an pg_dump archive with pg_restore will warn when
restoring a table with oid contents (and ignore the oid column)
- COPY will refuse to load binary dump that includes oids.
- pg_upgrade will error out when encountering tables declared WITH
OIDS, they have to be altered to remove the oid column first.
- Functionality to access the oid of the last inserted row (like
plpgsql's RESULT_OID, spi's SPI_lastoid, ...) has been removed.
The syntax for declaring a table WITHOUT OIDS (or WITH (oids = false)
for CREATE TABLE) is still supported. While that requires a bit of
support code, it seems unnecessary to break applications / dumps that
do not use oids, and are explicit about not using them.
The biggest user of WITH OID columns was postgres' catalog. This
commit changes all 'magic' oid columns to be columns that are normally
declared and stored. To reduce unnecessary query breakage all the
newly added columns are still named 'oid', even if a table's column
naming scheme would indicate 'reloid' or such. This obviously
requires adapting a lot code, mostly replacing oid access via
HeapTupleGetOid() with access to the underlying Form_pg_*->oid column.
The bootstrap process now assigns oids for all oid columns in
genbki.pl that do not have an explicit value (starting at the largest
oid previously used), only oids assigned later by oids will be above
FirstBootstrapObjectId. As the oid column now is a normal column the
special bootstrap syntax for oids has been removed.
Oids are not automatically assigned during insertion anymore, all
backend code explicitly assigns oids with GetNewOidWithIndex(). For
the rare case that insertions into the catalog via SQL are called for
the new pg_nextoid() function can be used (which only works on catalog
tables).
The fact that oid columns on system tables are now normal columns
means that they will be included in the set of columns expanded
by * (i.e. SELECT * FROM pg_class will now include the table's oid,
previously it did not). It'd not technically be hard to hide oid
column by default, but that'd mean confusing behavior would either
have to be carried forward forever, or it'd cause breakage down the
line.
While it's not unlikely that further adjustments are needed, the
scope/invasiveness of the patch makes it worthwhile to get merge this
now. It's painful to maintain externally, too complicated to commit
after the code code freeze, and a dependency of a number of other
patches.
Catversion bump, for obvious reasons.
Author: Andres Freund, with contributions by John Naylor
Discussion: https://postgr.es/m/20180930034810.ywp2c7awz7opzcfr@alap3.anarazel.de
2018-11-21 00:36:57 +01:00
|
|
|
prepared statement. The new table will be dropped at commit:
|
2006-02-19 01:04:28 +01:00
|
|
|
|
|
|
|
<programlisting>
|
|
|
|
PREPARE recentfilms(date) AS
|
|
|
|
SELECT * FROM films WHERE date_prod > $1;
|
Remove WITH OIDS support, change oid catalog column visibility.
Previously tables declared WITH OIDS, including a significant fraction
of the catalog tables, stored the oid column not as a normal column,
but as part of the tuple header.
This special column was not shown by default, which was somewhat odd,
as it's often (consider e.g. pg_class.oid) one of the more important
parts of a row. Neither pg_dump nor COPY included the contents of the
oid column by default.
The fact that the oid column was not an ordinary column necessitated a
significant amount of special case code to support oid columns. That
already was painful for the existing, but upcoming work aiming to make
table storage pluggable, would have required expanding and duplicating
that "specialness" significantly.
WITH OIDS has been deprecated since 2005 (commit ff02d0a05280e0).
Remove it.
Removing includes:
- CREATE TABLE and ALTER TABLE syntax for declaring the table to be
WITH OIDS has been removed (WITH (oids[ = true]) will error out)
- pg_dump does not support dumping tables declared WITH OIDS and will
issue a warning when dumping one (and ignore the oid column).
- restoring an pg_dump archive with pg_restore will warn when
restoring a table with oid contents (and ignore the oid column)
- COPY will refuse to load binary dump that includes oids.
- pg_upgrade will error out when encountering tables declared WITH
OIDS, they have to be altered to remove the oid column first.
- Functionality to access the oid of the last inserted row (like
plpgsql's RESULT_OID, spi's SPI_lastoid, ...) has been removed.
The syntax for declaring a table WITHOUT OIDS (or WITH (oids = false)
for CREATE TABLE) is still supported. While that requires a bit of
support code, it seems unnecessary to break applications / dumps that
do not use oids, and are explicit about not using them.
The biggest user of WITH OID columns was postgres' catalog. This
commit changes all 'magic' oid columns to be columns that are normally
declared and stored. To reduce unnecessary query breakage all the
newly added columns are still named 'oid', even if a table's column
naming scheme would indicate 'reloid' or such. This obviously
requires adapting a lot code, mostly replacing oid access via
HeapTupleGetOid() with access to the underlying Form_pg_*->oid column.
The bootstrap process now assigns oids for all oid columns in
genbki.pl that do not have an explicit value (starting at the largest
oid previously used), only oids assigned later by oids will be above
FirstBootstrapObjectId. As the oid column now is a normal column the
special bootstrap syntax for oids has been removed.
Oids are not automatically assigned during insertion anymore, all
backend code explicitly assigns oids with GetNewOidWithIndex(). For
the rare case that insertions into the catalog via SQL are called for
the new pg_nextoid() function can be used (which only works on catalog
tables).
The fact that oid columns on system tables are now normal columns
means that they will be included in the set of columns expanded
by * (i.e. SELECT * FROM pg_class will now include the table's oid,
previously it did not). It'd not technically be hard to hide oid
column by default, but that'd mean confusing behavior would either
have to be carried forward forever, or it'd cause breakage down the
line.
While it's not unlikely that further adjustments are needed, the
scope/invasiveness of the patch makes it worthwhile to get merge this
now. It's painful to maintain externally, too complicated to commit
after the code code freeze, and a dependency of a number of other
patches.
Catversion bump, for obvious reasons.
Author: Andres Freund, with contributions by John Naylor
Discussion: https://postgr.es/m/20180930034810.ywp2c7awz7opzcfr@alap3.anarazel.de
2018-11-21 00:36:57 +01:00
|
|
|
CREATE TEMP TABLE films_recent ON COMMIT DROP AS
|
2006-02-19 01:04:28 +01:00
|
|
|
EXECUTE recentfilms('2002-01-01');
|
2011-08-07 09:49:45 +02:00
|
|
|
</programlisting></para>
|
2005-01-09 06:57:45 +01:00
|
|
|
</refsect1>
|
|
|
|
|
2001-10-22 20:14:47 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Compatibility</title>
|
2001-03-20 21:54:41 +01:00
|
|
|
|
|
|
|
<para>
|
2005-11-01 22:09:51 +01:00
|
|
|
<command>CREATE TABLE AS</command> conforms to the <acronym>SQL</acronym>
|
2008-10-28 15:09:45 +01:00
|
|
|
standard. The following are nonstandard extensions:
|
2004-09-23 05:43:57 +02:00
|
|
|
|
|
|
|
<itemizedlist spacing="compact">
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The standard requires parentheses around the subquery clause; in
|
|
|
|
<productname>PostgreSQL</productname>, these parentheses are
|
|
|
|
optional.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2008-10-28 15:09:45 +01:00
|
|
|
In the standard, the <literal>WITH [ NO ] DATA</literal> clause
|
|
|
|
is required; in PostgreSQL it is optional.
|
2005-11-01 22:09:51 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
2017-10-09 03:44:17 +02:00
|
|
|
<para><productname>PostgreSQL</productname> handles temporary tables in a way
|
2006-07-04 20:07:24 +02:00
|
|
|
rather different from the standard; see
|
2017-11-23 15:39:47 +01:00
|
|
|
<xref linkend="sql-createtable"/>
|
2006-07-04 20:07:24 +02:00
|
|
|
for details.
|
2005-11-01 22:09:51 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
The <literal>WITH</literal> clause is a <productname>PostgreSQL</productname>
|
Remove WITH OIDS support, change oid catalog column visibility.
Previously tables declared WITH OIDS, including a significant fraction
of the catalog tables, stored the oid column not as a normal column,
but as part of the tuple header.
This special column was not shown by default, which was somewhat odd,
as it's often (consider e.g. pg_class.oid) one of the more important
parts of a row. Neither pg_dump nor COPY included the contents of the
oid column by default.
The fact that the oid column was not an ordinary column necessitated a
significant amount of special case code to support oid columns. That
already was painful for the existing, but upcoming work aiming to make
table storage pluggable, would have required expanding and duplicating
that "specialness" significantly.
WITH OIDS has been deprecated since 2005 (commit ff02d0a05280e0).
Remove it.
Removing includes:
- CREATE TABLE and ALTER TABLE syntax for declaring the table to be
WITH OIDS has been removed (WITH (oids[ = true]) will error out)
- pg_dump does not support dumping tables declared WITH OIDS and will
issue a warning when dumping one (and ignore the oid column).
- restoring an pg_dump archive with pg_restore will warn when
restoring a table with oid contents (and ignore the oid column)
- COPY will refuse to load binary dump that includes oids.
- pg_upgrade will error out when encountering tables declared WITH
OIDS, they have to be altered to remove the oid column first.
- Functionality to access the oid of the last inserted row (like
plpgsql's RESULT_OID, spi's SPI_lastoid, ...) has been removed.
The syntax for declaring a table WITHOUT OIDS (or WITH (oids = false)
for CREATE TABLE) is still supported. While that requires a bit of
support code, it seems unnecessary to break applications / dumps that
do not use oids, and are explicit about not using them.
The biggest user of WITH OID columns was postgres' catalog. This
commit changes all 'magic' oid columns to be columns that are normally
declared and stored. To reduce unnecessary query breakage all the
newly added columns are still named 'oid', even if a table's column
naming scheme would indicate 'reloid' or such. This obviously
requires adapting a lot code, mostly replacing oid access via
HeapTupleGetOid() with access to the underlying Form_pg_*->oid column.
The bootstrap process now assigns oids for all oid columns in
genbki.pl that do not have an explicit value (starting at the largest
oid previously used), only oids assigned later by oids will be above
FirstBootstrapObjectId. As the oid column now is a normal column the
special bootstrap syntax for oids has been removed.
Oids are not automatically assigned during insertion anymore, all
backend code explicitly assigns oids with GetNewOidWithIndex(). For
the rare case that insertions into the catalog via SQL are called for
the new pg_nextoid() function can be used (which only works on catalog
tables).
The fact that oid columns on system tables are now normal columns
means that they will be included in the set of columns expanded
by * (i.e. SELECT * FROM pg_class will now include the table's oid,
previously it did not). It'd not technically be hard to hide oid
column by default, but that'd mean confusing behavior would either
have to be carried forward forever, or it'd cause breakage down the
line.
While it's not unlikely that further adjustments are needed, the
scope/invasiveness of the patch makes it worthwhile to get merge this
now. It's painful to maintain externally, too complicated to commit
after the code code freeze, and a dependency of a number of other
patches.
Catversion bump, for obvious reasons.
Author: Andres Freund, with contributions by John Naylor
Discussion: https://postgr.es/m/20180930034810.ywp2c7awz7opzcfr@alap3.anarazel.de
2018-11-21 00:36:57 +01:00
|
|
|
extension; storage parameters are not in the standard.
|
2004-09-23 05:43:57 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
2006-02-19 01:04:28 +01:00
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The <productname>PostgreSQL</productname> concept of tablespaces is not
|
|
|
|
part of the standard. Hence, the clause <literal>TABLESPACE</literal>
|
|
|
|
is an extension.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
2011-08-07 09:49:45 +02:00
|
|
|
</itemizedlist></para>
|
2001-10-22 20:14:47 +02:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>See Also</title>
|
|
|
|
|
|
|
|
<simplelist type="inline">
|
2017-11-23 15:39:47 +01:00
|
|
|
<member><xref linkend="sql-creatematerializedview"/></member>
|
|
|
|
<member><xref linkend="sql-createtable"/></member>
|
|
|
|
<member><xref linkend="sql-execute"/></member>
|
|
|
|
<member><xref linkend="sql-select"/></member>
|
|
|
|
<member><xref linkend="sql-selectinto"/></member>
|
|
|
|
<member><xref linkend="sql-values"/></member>
|
2001-10-22 20:14:47 +02:00
|
|
|
</simplelist>
|
|
|
|
</refsect1>
|
2010-11-23 21:27:50 +01:00
|
|
|
|
1999-06-14 09:37:05 +02:00
|
|
|
</refentry>
|