| From: | NikhilS <nikkhils(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Neil Conway" <neilc(at)samurai(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Trevor Hardcastle" <chizu(at)spicious(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: CREATE TABLE LIKE INCLUDING INDEXES support |
| Date: | 2007-05-20 06:34:37 |
| Message-ID: | d3c4af540705192334m208fb311ubccbe77fdf899db7@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Hi,
> > Since this patch is going to consider creating unique/primary indexes
> > assuming them to be constraints,
>
> If it does that it will be rejected. There is a difference here and
> that difference has to be maintained.
>
> The correct way to think about this is that a pg_constraint entry of
> type "unique" or "primary key" has an associated index that is part of
> its implementation (and therefore has an "internal" dependency on the
> constraint). But they are far from being the same thing.
Thanks Tom, I understand the difference now. I have a working patch and will
send it to Neil for review tommorrow.
Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Bjorklund | 2007-05-20 07:44:54 | Re: UTF8MatchText |
| Previous Message | Shachar Shemesh | 2007-05-20 05:43:08 | Re: Re: [Oledb-dev] double precision error with pg linux server, but not with windows pg server |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Bjorklund | 2007-05-20 07:44:54 | Re: UTF8MatchText |
| Previous Message | Jaime Casanova | 2007-05-20 00:11:54 | Re: Updateable cursors patch |