From: mark <dvlhntr@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Deferred constraints performance impact ?
Date: Thu, 19 Jul 2012 20:27:38 -0600
Message-ID: <01a701cd661f$3cc05770$b6410650$@com> (raw)
Hi all,
We have put some deferred constraints (some initially immediate, some
initially deferred) into our database for testing with our applications.
I haven't seen any noticeable loss in performance, but I am not sure I can
properly simulate our full production environment load levels in my tests.
I was wondering if I am turning on something that has known significant
negative impacts to performance, just from having them there.
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.
Anyways, just looking for feedback if anyone has any.
-Mark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dvlhntr@gmail.com
Subject: Re: Deferred constraints performance impact ?
In-Reply-To: <01a701cd661f$3cc05770$b6410650$@com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox