| From: | NikhilS <nikkhils(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <bruce(at)momjian(dot)us> |
| Cc: | ioguix(at)free(dot)fr, pgsql-bugs(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] BUG #3774: create table like including index doesn't update pg_constraints with primary key |
| Date: | 2007-12-02 08:14:20 |
| Message-ID: | d3c4af540712020014y10b0589bg17103dfd1175108d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hi,
>
> > The fundamental question though is should we allow primary, unique
> > CONSTRAINTS which use the index mechanism just as an implementation to
> be
> > created using the "INCLUDING INDEXES" mechanism.
>
> Yeah, this bizarreness was foreseen and agreed to back when we set up
> LIKE INCLUDING CONSTRAINTS the way it was defined (ie, copying only
> CHECK constraints and not other things called constraints). I was never
> very thrilled with that definition myself, but it's a bit too late to
> revisit it.
>
Yeah this is all confusing. I believe we should remove the following TODO
now that the above has been checked in:
CREATE
- Have WITH CONSTRAINTS also create constraint indexes
http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php
Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lou Duchez | 2007-12-02 20:01:41 | BUG #3795: pg_dump is mis-dumping columns containing line breaks |
| Previous Message | Tom Lane | 2007-12-02 03:48:22 | Re: BUG #3792: cluster in UTF deny database in LATIN2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2007-12-02 08:29:18 | Re: String encoding during connection "handshake" |
| Previous Message | Steve Singer | 2007-12-02 06:51:09 | Re: Re: [HACKERS] [GENERAL] plperl and regexps with accented characters - incompatible? |