Defines a new table from the results of a query.

Synopsis

  1. [ WITH [ RECURSIVE ] <with_query> [, ...] ]
  2. SELECT [ALL | DISTINCT [ON ( <expression> [, ...] )]]
  3. * | <expression> [AS <output_name>] [, ...]
  4. INTO [TEMPORARY | TEMP | UNLOGGED ] [TABLE] <new_table>
  5. [FROM <from_item> [, ...]]
  6. [WHERE <condition>]
  7. [GROUP BY <expression> [, ...]]
  8. [HAVING <condition> [, ...]]
  9. [{UNION | INTERSECT | EXCEPT} [ALL | DISTINCT ] <select>]
  10. [ORDER BY <expression> [ASC | DESC | USING <operator>] [NULLS {FIRST | LAST}] [, ...]]
  11. [LIMIT {<count> | ALL}]
  12. [OFFSET <start> [ ROW | ROWS ] ]
  13. [FETCH { FIRST | NEXT } [ <count> ] { ROW | ROWS } ONLY ]
  14. [FOR {UPDATE | SHARE} [OF <table_name> [, ...]] [NOWAIT]
  15. [...]]

Description

SELECT INTO creates a new table and fills it with data computed by a query. The data is not returned to the client, as it is with a normal SELECT. The new table’s columns have the names and data types associated with the output columns of the SELECT.

Parameters

The majority of parameters for SELECT INTO are the same as SELECT.

TEMPORARY

TEMP

If specified, the table is created as a temporary table.

UNLOGGED

If specified, the table is created as an unlogged table. Data written to unlogged tables is not written to the write-ahead (WAL) log, which makes them considerably faster than ordinary tables. However, the contents of an unlogged table are not replicated to mirror segment instances. Also an unlogged table is not crash-safe. After a segment instance crash or unclean shutdown, the data for the unlogged table on that segment is truncated. Any indexes created on an unlogged table are automatically unlogged as well.

new_table

The name (optionally schema-qualified) of the table to be created.

Examples

Create a new table films_recent consisting of only recent entries from the table films:

  1. SELECT * INTO films_recent FROM films WHERE date_prod >=
  2. '2016-01-01';

Compatibility

The SQL standard uses SELECT INTO to represent selecting values into scalar variables of a host program, rather than creating a new table. The Greenplum Database usage of SELECT INTO to represent table creation is historical. It is best to use CREATE TABLE AS for this purpose in new applications.

See Also

SELECT, CREATE TABLE AS

Parent topic: SQL Commands