Re: What is postgresql doing for "statement: commit;begin;" - Mailing list pgsql-general

From Nick Burch
Subject Re: What is postgresql doing for "statement: commit;begin;"
Date
Msg-id Pine.LNX.4.44.0501171611560.2265-100000@localhost.localdomain
Whole thread Raw
In response to Re: What is postgresql doing for "statement: commit;begin;"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Mon, 17 Jan 2005, Tom Lane wrote:
> Nick Burch <nick@torchbox.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


pgsql-general by date:

Previous
From: "Frank D. Engel, Jr."
Date:
Subject: Re: Problem with win32 installer for PG 8.0
Next
From: Együd Csaba
Date:
Subject: Any function for calculating inersect of intervals?