| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Andrew Geery <andrew(dot)geery(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch |
| Date: | 2011-06-16 17:34:22 |
| Message-ID: | BANLkTi=71xatSXLEHxLQ5U3d75_vQ=TpQA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 16, 2011 at 1:25 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Possible solution is to leave bootstrap's behavior alone, and have a
> step during initdb's post-bootstrap stuff that creates a matching
> pg_constraint row for every pg_attribute entry that's marked attnotnull.
That seems like a pretty good solution.
> I have a feeling that omitting these entries for system catalogs would
> bite us in other ways down the road, even if inheritance were the only
> soft spot right now.
I share that feeling.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-06-16 17:45:12 | Re: use less space in xl_xact_commit patch |
| Previous Message | Dan Ports | 2011-06-16 17:33:56 | Re: patch: update README-SSI |