On Fri, Jul 20, 2012 at 4:27 AM, mark <dvlh...@gmail.com> wrote: > We have put some deferred constraints (some initially immediate, some > initially deferred) into our database for testing with our applications.
> I understand a lot more may have to be tracked through a transaction and > there could be some impact from that. Similar to an after update trigger? Or > are the two not comparable in terms of impact from what is tracked and then > checked. Another factor might be the amount of constraint violations you expect: if there are many then deferring the check can create much more work for the DB because you issue more DML as with a non deferred constraint which could create errors much sooner and hence make you stop sending DML earlier. Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
