2010/1/18 Tom Lane :
> Dean Rasheed writes:
>> Agreed. That's much neater. However, it does introduce a change in
>> behaviour - if you have 2 constraints with the same name in different
>> schemas, one deferrable, and one not, and the non-deferrable one is
>> first on the search path, then you'll
Dean Rasheed writes:
> Agreed. That's much neater. However, it does introduce a change in
> behaviour - if you have 2 constraints with the same name in different
> schemas, one deferrable, and one not, and the non-deferrable one is
> first on the search path, then you'll get an error if you try to
2010/1/17 Tom Lane :
> I want to do something about the open item discussed in this thread:
> http://archives.postgresql.org/message-id/2009081446.ga25...@depesz.com
>
> The right way to handle that, IMO, is to create pg_constraint rows for
> triggers created via CREATE CONSTRAINT TRIGGER. The
