>> Comments and further feedback, if any, appreciated.
> Did you look at how this conflicts with my patch to add not null
> rows to pg_constraint?
I was certainly not aware of this patch in the commitfest. Your patch
has a larger footprint with more functional changes in it. IMHO, it
will be easiest to queue this non-inheritable constraints patch behind
your patch in the commitfest. There will be certain bitrot, which I
can fix once your patch gets committed.
In response to
pgsql-hackers by date
|Next:||From: jordani||Date: 2011-07-30 05:23:44|
|Subject: Re: Incremental checkopints|
|Previous:||From: Peter Geoghegan||Date: 2011-07-30 00:48:03|
|Subject: Re: Reduced power consumption in autovacuum launcher process|