| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "NikhilS" <nikkhils(at)gmail(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Chris Fischer" <Chris(dot)Fischer(at)channeladvisor(dot)com>, <pgsql-bugs(at)postgresql(dot)org>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Problem identifying constraints which should not be inherited |
| Date: | 2008-03-27 11:52:26 |
| Message-ID: | 47EB8A7A.9010208@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
NikhilS wrote:
> Am important decision here is about adding a new attribute to pg_constraint
> as it is the only sane way of determining inherited constraints, but that
> will require an initdb. Comments?
There's no problem forcing an initdb at this point in the release cycle.
We will do that for sure many times before we reach beta stage.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-27 15:24:29 | Re: Problem identifying constraints which should not be inherited |
| Previous Message | NikhilS | 2008-03-27 11:14:19 | Re: Problem identifying constraints which should not be inherited |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2008-03-27 12:15:48 | Re: Script binaries renaming |
| Previous Message | Alvaro Herrera | 2008-03-27 11:14:57 | Re: [DOCS] pg_total_relation_size() and CHECKPOINT |