Hello Tom,
I can confirm that adding the indexes used by the deferred constraint
triggers solved the issue.
Thank you very much for your suggestions.
Best regards,
Giulio Cesare
On 10/24/07, Giulio Cesare Solaroli [EMAIL PROTECTED] wrote:
On 10/24/07, Tom Lane [EMAIL PROTECTED] wrote:
Giulio Cesare Solaroli [EMAIL PROTECTED] writes:
As you may notice, the commit phase takes almost 2 full minutes. :-(
Yow. It's hard to believe that the actual commit (ie, flushing the
commit record to WAL) could take more than a fraction of a second.
I'm thinking there must be a pile of
Giulio Cesare Solaroli [EMAIL PROTECTED] writes:
How can I try to isolate the trigger taking so long, in oder to
understand which is/are the missing index(es)?
Try SET CONSTRAINTS ALL IMMEDIATE and then EXPLAIN ANALYZE the
delete. This should cause all the triggers to run within the
scope of
On 10/24/07, Tom Lane [EMAIL PROTECTED] wrote:
Giulio Cesare Solaroli [EMAIL PROTECTED] writes:
How can I try to isolate the trigger taking so long, in oder to
understand which is/are the missing index(es)?
Try SET CONSTRAINTS ALL IMMEDIATE and then EXPLAIN ANALYZE the
delete. This should
