Re: ADD/DROP INHERITS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Hannu Krosing <hannu(at)skype(dot)net>, Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ADD/DROP INHERITS
Date: 2006-06-08 17:01:14
Message-ID: 28932.1149786074@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Stark <gsstark(at)mit(dot)edu> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> The implementation I had in mind was to add columns similar to attinhcount
>> and attislocal to pg_constraint.

> Hm that would be simpler. That still leaves NOT NULL as a bit of a headache.

Yeah, I think we would want to start storing NOT NULL constraints
explicitly in pg_constraint so that we could track them. This would
allow fixing some other things too, like the fact that we fail to
remember names for NOT NULL constraints. attnotnull might still be
useful as an optimization, or maybe it should just go away.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-06-08 17:11:27 Re: Type of bare text strings
Previous Message Tom Lane 2006-06-08 16:56:17 Re: That EXPLAIN ANALYZE patch still needs work