Re: Patch: Extend NOT NULL representation to pg_constraint - Mailing list pgsql-hackers

From Bernd Helmle
Subject Re: Patch: Extend NOT NULL representation to pg_constraint
Date
Msg-id A883EE6393BBD2B515D38C81@amenophis
Whole thread Raw
In response to Re: Patch: Extend NOT NULL representation to pg_constraint  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Patch: Extend NOT NULL representation to pg_constraint
List pgsql-hackers

--On 26. September 2010 15:50:06 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote:

>> I think his question was - how do we feel about the massive catalog
>> bloat this patch will create?
>
> It's a fair question.
>
> I can imagine designing things so that we don't create an explicit
> pg_constraint row for the simplest case of an unnamed, non-inherited
> NOT NULL constraint.  Seems like it would complicate matters quite
> a lot though, in exchange for saving what in the end isn't an enormous
> amount of space.

What i can try is to record the inheritance information only in case of 
attinhcount > 0. This would make maintenance of the pg_constraint records 
for NOT NULL columns a little complicater though. Another thing we should 
consider is that Peter's functional dependency patch was supposed to rely 
on this feature (1), once it gets done. Not sure this still holds true....

1) 
<http://archives.postgresql.org/message-id/1279361718.17928.1.camel@vanquo.pezone.net>

-- 
Thanks
Bernd


pgsql-hackers by date:

Previous
From: Marios Vodas
Date:
Subject: gist access methods parameter types
Next
From: Devrim GÜNDÜZ
Date:
Subject: A small update for postgresql.conf.sample