From: | Nick Burch <nick(at)torchbox(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: What is postgresql doing for "statement: commit;begin;" |
Date: | 2005-01-17 16:25:09 |
Message-ID: | Pine.LNX.4.44.0501171611560.2265-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 17 Jan 2005, Tom Lane wrote:
> Nick Burch <nick(at)torchbox(dot)com> writes:
> > Quite a lot, I'm seeing lines like:
> > 2005-01-17 13:11:15 LOG: duration: 4688.108 ms statement: commit;begin;
>
> > Is there any way to find out what exactly got executed here?
>
> A whole lot of deferred-until-transaction-commit operations, evidently.
> You got any deferred foreign keys in this database?
No, we don't. Because of this, I did some reading and discovered
"log_statement" and "log_pid", and turned them on.
It appears that ColdFusion is wrapping some of it's internal housekeeping
DB calls in transactions, and these are the ones that then show up as the
long running "statement: commit;begin;" entries. Mystery solved.
Thanks
Nick
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-01-17 16:37:27 | Re: Any function for calculating inersect of intervals? |
Previous Message | Együd Csaba | 2005-01-17 16:24:49 | Any function for calculating inersect of intervals? |