On Sep 27, 2011, at 6:37 PM, Craig Ringer wrote:
> On 09/27/2011 12:54 PM, Ben Chobot wrote:
>>
>> My memory is fuzzy but as I recall, a possible downside to using
>> deferred constraints was increased memory usage
>
> That's right. PostgreSQL doesn't currently support spilling of pending
> con
On 09/27/2011 12:54 PM, Ben Chobot wrote:
On Sep 26, 2011, at 10:52 AM, Maria L. Wilson wrote:
Our first try to solve this problem has been to convert these triggers
into a constraint trigger which allows for DEFERRABLE INITIALLY
DEFERRED flags. This, we are finding, is forcing the trigger func
On Sep 26, 2011, at 10:52 AM, Maria L. Wilson wrote:
> Our first try to solve this problem has been to convert these triggers into a
> constraint trigger which allows for DEFERRABLE INITIALLY DEFERRED flags.
> This, we are finding, is forcing the trigger function to run after the
> triggering
Hi all
I would like to start a dialogue and hear general feedback about the use
of constraint triggers in postgres (8.4.5).
Our overall issue is that using general triggers is causing slow inserts
(from locking issues) in our database. Here are some details:
A little background (jboss/
