postgres.git / summary / log / commit / refs

commit    de87d4704432e98a327dbf42dbc4711fa2628a9c
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Sun Aug 26 20:33:11 2012 +0000
First released in: 9.3.0

    Clarify documentation that primary key and unique constraints are copied
    for CREATE TABLE LIKE ... INCLUDING INDEXES.
    
    Per report from david.sahagian@emc.com


doc/src/sgml/ref/create_table.sgml | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 19e6f8ed610..445ca406950 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -336,16 +336,13 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <para> Not-null constraints are always copied to the new table. - <literal>CHECK</literal> constraints will only be copied if - <literal>INCLUDING CONSTRAINTS</literal> is specified; other types of - constraints will never be copied. Also, no distinction is made between - column constraints and table constraints &mdash; when constraints are - requested, all check constraints are copied. - </para> - <para> - Any indexes on the original table will not be created on the new - table, unless the <literal>INCLUDING INDEXES</literal> clause is - specified. + <literal>CHECK</literal> constraints will be copied only if + <literal>INCLUDING CONSTRAINTS</literal> is specified. + Indexes, <literal>PRIMARY KEY</>, and <literal>UNIQUE</> constraints + on the original table will be created on the new table only if the + <literal>INCLUDING INDEXES</literal> clause is specified. + No distinction is made between column constraints and table + constraints. </para> <para><literal>STORAGE</> settings for the copied column definitions will only be copied if <literal>INCLUDING STORAGE</literal> is specified. The [parent: 9e9a5b71d56a]