</refsect1>

</refentry>

<REFENTRY ID="SQL-CREATETABLEAS">

<REFMETA>

<REFENTRYTITLE>

CREATE TABLE

</REFENTRYTITLE>

<REFMISCINFO>SQL - Language Statements</REFMISCINFO>

</REFMETA>

<REFNAMEDIV>

<REFNAME>

CREATE TABLE

</REFNAME>

<REFPURPOSE>

Creates a new table

</REFPURPOSE>

<REFSYNOPSISDIV>

<REFSYNOPSISDIVINFO>

<DATE>1998-09-22</DATE>

</REFSYNOPSISDIVINFO>

<SYNOPSIS>

CREATE TABLE <REPLACEABLE CLASS="PARAMETER">table</REPLACEABLE> [ ( <REPLACEABLE CLASS="PARAMETER">column</REPLACEABLE> [, ...] ) ] AS <REPLACEABLE CLASS="PARAMETER">select_clause</REPLACEABLE>

</SYNOPSIS>

<REFSECT2 ID="R2-SQL-CREATETABLEAS-1">

<REFSECT2INFO>

<DATE>1998-09-22</DATE>

</REFSECT2INFO>

<TITLE>

Inputs

</TITLE>

<PARA>

<VARIABLELIST>

<VARLISTENTRY>

<TERM>

<REPLACEABLE CLASS="PARAMETER">table</REPLACEABLE>

</TERM>

<LISTITEM>

<PARA>

The name of a new table to be created.

</PARA>

</LISTITEM>

</VARLISTENTRY>

<VARLISTENTRY>

<TERM>

<REPLACEABLE CLASS="PARAMETER">column</REPLACEABLE>

</TERM>

<LISTITEM>

<PARA>

The name of a column. Multiple column names can be specified using

a comma-delimited list of column names.

</PARA>

</LISTITEM>

</VARLISTENTRY>

<VARLISTENTRY>

<TERM>

<REPLACEABLE CLASS="PARAMETER">select_clause</REPLACEABLE>

</TERM>

<LISTITEM>

<PARA>

A valid query statement. Refer to SELECT for a description of the

allowed syntax.

</PARA>

</LISTITEM>

</VARLISTENTRY>

</VARIABLELIST>

<REFSECT2 ID="R2-SQL-CREATETABLEAS-2">

<REFSECT2INFO>

<DATE>1998-09-22</DATE>

</REFSECT2INFO>

<TITLE>

Outputs

</TITLE>

<PARA>

Refer to CREATE TABLE and SELECT for a summary of possible output

messages.

<REFSECT1 ID="R1-SQL-CREATETABLEAS-1">

<REFSECT1INFO>

<DATE>1998-09-22</DATE>

</REFSECT1INFO>

<TITLE>

Description

</TITLE>

<PARA>

CREATE TABLE AS enables a table to be created from the contents of

an existing table. It has functionality equivalent to SELECT TABLE INTO,

but with perhaps a more obvious syntax.

</refsect1>

</refentry>

<!-- Keep this comment at the end of the file

Local variables:

mode: sgml

EXPLAIN

</REFNAME>

<REFPURPOSE>

Shows statement execution details.

Shows statement execution details

</REFPURPOSE>

<REFSYNOPSISDIV>

<VARLISTENTRY>

<TERM>

NOTICE: QUERY PLAN:

<replaceable>plan</replaceable>

</TERM>

<LISTITEM>

<PARA>

Explicit query plan from the <productname>Postgres</productname> backend.

<VARIABLELIST>

<VARLISTENTRY>

<TERM>

<replaceable>status</replaceable>

</TERM>

<LISTITEM>

<PARA>

<VARLISTENTRY>

<TERM>

EXPLAIN

<PARA>

Flag sent after query plan is shown.

</VARIABLELIST>

</VARIABLELIST>

</REFSECT2>

Notes

</TITLE>

<PARA>

There is only sparse documentation on the optimizer's use of cost

information in <productname>Postgres</productname>.

General information on cost estimation for query optimization

can be found in database textbooks.

Refer to the <citetitle>Programmer's Guide</citetitle>

in the chapters on indexes and the genetic query optimizer for

more information.

</REFSECT2>

</TERM>

<LISTITEM>

<PARA>

If <REPLACEABLE CLASS="PARAMETER">cursor</REPLACEABLE> is not previously declared.

If <REPLACEABLE CLASS="PARAMETER">cursor</REPLACEABLE>

is not previously declared.

The cursor must be declared within a transaction block.

<VARLISTENTRY>

Compatibility

</TITLE>

<PARA>

The non-embedded use of cursors is a <productname>Postgres</productname>

extension. The syntax and usage of cursors is being compared

against the embedded form of cursors defined in <acronym>SQL92</acronym>.

</PARA>

<REFSECT2 ID="R2-SQL-FETCH-4">

SQL92

</TITLE>

<PARA>

SQL92 allows absolute positioning of the cursor for

<acronym>SQL92</acronym> allows absolute positioning of the cursor for

FETCH, and allows placing the results into explicit variables.

<synopsis>

<REFSYNOPSISDIV>

<REFSYNOPSISDIVINFO>

<DATE>1998-04-15</DATE>

<DATE>1998-09-23</DATE>

</REFSYNOPSISDIVINFO>

<SYNOPSIS>

GRANT <REPLACEABLE CLASS="PARAMETER">privilege</REPLACEABLE> [, ...]

<REFSECT2 ID="R2-SQL-GRANT-1">

<REFSECT2INFO>

<DATE>1998-09-01</DATE>

<DATE>1998-09-23</DATE>

</REFSECT2INFO>

<TITLE>

Inputs

<REFSECT2 ID="R2-SQL-GRANT-2">

<REFSECT2INFO>

<DATE>1998-09-01</DATE>

<DATE>1998-09-23</DATE>

</REFSECT2INFO>

<TITLE>

Outputs

</TITLE>

<PARA>

<VARIABLELIST>

<VARLISTENTRY>

<TERM>

<replaceable>status</replaceable>

</TERM>

<LISTITEM>

<PARA>

<VARIABLELIST>

<VARLISTENTRY>

<TERM>

to give privileges to the specified group or users.

</VARIABLELIST>

</VARIABLELIST>

</REFSECT2>

</REFSYNOPSISDIV>

<REFSECT1 ID="R1-SQL-GRANT-1">

<REFSECT1INFO>

<DATE>1998-09-01</DATE>

<DATE>1998-09-23</DATE>

</REFSECT1INFO>

<TITLE>

Description

<REFSECT2 ID="R2-SQL-GRANT-3">

<REFSECT2INFO>

<DATE>1998-09-01</DATE>

<DATE>1998-09-23</DATE>

</REFSECT2INFO>

<TITLE>

Notes

Currently, to create a GROUP you have to insert

data manually into table pg_group as:

<programlisting>

INSERT INTO pg_group VALUES ('todos');

CREATE USER miriam IN GROUP todos;

INSERT INTO pg_group VALUES ('todos');

CREATE USER miriam IN GROUP todos;

</programlisting>

Refer to REVOKE statements to revoke access privileges.

</tip>

</TITLE>

<PARA>

<ProgramListing>

-- grant insert privilege to all users on table films:

--

GRANT INSERT ON films TO PUBLIC;

-- grant insert privilege to all users on table films:

--

GRANT INSERT ON films TO PUBLIC;

</programlisting>

<programlisting>

-- grant all privileges to user manuel on view kinds:

--

GRANT ALL ON kinds TO manuel;

-- grant all privileges to user manuel on view kinds:

--

GRANT ALL ON kinds TO manuel;

</ProgramListing>

</REFSECT1>

<REFSECT2 ID="R2-SQL-GRANT-4">

<REFSECT2INFO>

<DATE>1998-09-01</DATE>

<DATE>1998-09-23</DATE>

</REFSECT2INFO>

<TITLE>

SQL92

</TITLE>

<PARA>

The SQL92 syntax for GRANT allows setting privileges

The<acronym>SQL92</acronym> syntax for GRANT allows setting privileges

for individual columns

within a table, and allows setting a privilege to grant

the same privileges to others.