On sön, 2010-09-05 at 11:35 -0400, Tom Lane wrote: > Dean Rasheed <dean.a.rash...@gmail.com> writes: > > On 5 September 2010 16:15, Tom Lane <t...@sss.pgh.pa.us> wrote: > >> I don't recall having thought about it one way or the other. What did > >> the check look like? > > > Well originally it was searching indexes rather than constraints, and > > funcdeps_check_pk() included the following check: > > > if (!indexStruct->indisprimary || !indexStruct->indimmediate) > > continue; > > > Now its looping over pg_constraint entries, so I guess anything wtih > > con->condeferrable == true should be ignored. > > Seems reasonable, will fix. Thanks for the report!
Yes, the SQL standard explicitly requires the constraint in question to be immediate. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
