On Thu, Jun 16, 2011 at 1:25 PM, Tom Lane <t...@sss.pgh.pa.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
