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:
>
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.
"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
Hello Tom,
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 mor
"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 pr
Hello,
I am having a strange latency problem on my instance of Postgres that
I don't know how to investigate.
I am accessing the db instance using a Java application and the
Cayenne mapping framework. Everything works fine, except when it is
time to delete a user account (that is a user of the ap
