From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christoph Haller <ch@rodos.fzk.de>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: BEGIN-cascade blocks application
Date: Fri, 02 Apr 2004 10:33:40 -0500
Message-ID: <27774.1080920020@sss.pgh.pa.us> (raw)
In-Reply-To: <200404021032.MAA07447@rodos>
References: <200404021032.MAA07447@rodos>
Christoph Haller <ch@rodos.fzk.de> writes:
> I've turned on statement logging to find out
> about the last one being processed. It was
> BEGIN;
> WARNING: BEGIN: already a transaction in progress
> It was the last of a cascade of duplicate BEGINs,
> and the only reason I could see for the application being blocked
> was this cascade.
I don't think so. An extra BEGIN is a complete no-op except for
issuing that warning message.
> I eliminated those duplicates and now the
> application runs without any stops.
You fixed a bug in your application logic, then. Or maybe the bug is
still there but happened not to be triggered in your second test.
Just to check, I fired 100000 consecutive "BEGIN;"s at PG 7.3.6 on
HPUX 10.20, and didn't see any particular hiccup... and no, I don't
think this was affected by any bugfixes between 7.3.4 and 7.3.6 ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, ch@rodos.fzk.de
Subject: Re: BEGIN-cascade blocks application
In-Reply-To: <27774.1080920020@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox