From: <david.sahagian@emc.com>
To: <magnus@hagander.net>
CC: <pgsql-docs@postgresql.org>
Date: Mon, 2 Jan 2012 09:32:39 -0500
Subject: Re: CREATE TABLE LIKE, regarding constraints
Thread-Topic: [DOCS] CREATE TABLE LIKE, regarding constraints
Thread-Index: AczHudrN740kGUtpR9uTE7s7pbpWpABn261g
Message-ID: <F3CBFBA88397EA498B22A05FFA9EC49D60A412F0@MX22A.corp.emc.com>
References: <F3CBFBA88397EA498B22A05FFA9EC49D60A4123A@MX22A.corp.emc.com>
	<CABUevExTjCDGhskyXid+6pHSoatUO2u0L7zJ-jAJf43WaLMmtg@mail.gmail.com>
In-Reply-To: 
 <CABUevExTjCDGhskyXid+6pHSoatUO2u0L7zJ-jAJf43WaLMmtg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

-----Original Message-----
From: Magnus Hagander [mailto:magnus@hagander.net]=20
Sent: Saturday, December 31, 2011 7:42 AM
To: Sahagian, David
Cc: pgsql-docs@postgresql.org
Subject: Re: [DOCS] CREATE TABLE LIKE, regarding constraints

On Fri, Dec 30, 2011 at 22:27,  <david.sahagian@emc.com> wrote:
> www.postgresql.org/docs/9.0/static/sql-createtable.html
> =3D=3D =3D=3D =3D=3D =3D=3D =3D=3D
> LIKE parent_table [ like_option ... ]
> . . .
> Not-null constraints are always copied to the new table.
> CHECK constraints will only be copied if INCLUDING CONSTRAINTS is specifi=
ed; other types of constraints will never be copied.
> . . .
> =3D=3D =3D=3D =3D=3D =3D=3D =3D=3D
>
> But I do see PK and UNIQUE constraints
> =A0CONSTRAINT blah_pkey PRIMARY KEY (id),
> =A0CONSTRAINT blah_host_id_key UNIQUE (host_id)
> in the def of the new table.

Can you provide the commands you ran to make that happen? It doesn't
happen for me in a trivial test.

> Also, why is there no discussion of what "EXCLUDING CONSTRAINTS" will res=
ult in ?

--=20
=A0Magnus Hagander
=A0Me: http://www.hagander.net/
=A0Work: http://www.redpill-linpro.com/


Magnus,=20
I did some more "testing" of CREATE TABLE LIKE,=20
and now see that [INCLUDING INDEXES] also can cause PRIMARY KEY and UNIQUE =
constraints to become part of the new table.

++++++++++++++
 CREATE TABLE yesConstr_noIndex_tbl (
   like mytbl=20
   INCLUDING DEFAULTS  INCLUDING CONSTRAINTS                     INCLUDING =
STORAGE=20
 );
++++++++++++++
  no PRIMARY KEY
  no UNIQUE
  no indexes

++++++++++++++
 CREATE TABLE  noConstr_yesIndex_tbl (
   like mytbl=20
   INCLUDING DEFAULTS                        INCLUDING INDEXES   INCLUDING =
STORAGE=20
 );
++++++++++++++
  NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "mytbl_pke=
y"           for table "mytbl"
  NOTICE:  CREATE TABLE / UNIQUE      will create implicit index "mytbl_hos=
t_id_key"    for table "mytbl"

  CONSTRAINT mytbl_pkey PRIMARY KEY (id),
  CONSTRAINT mytbl_host_id_key UNIQUE (host_id)
  and 2 unrelated indexes: (a_diff_col) (yet_a_diff_col)


I have no problem with this behavior,=20
but the doc probably deserves some clarification on the "relationship" betw=
een=20
[INCLUDING CONSTRAINTS] and [INCLUDING INDEXES].

Thanks,
-dvs-