From: Christoph Haller <ch@rodos.fzk.de>
To: pgsql-interfaces@postgresql.org
Subject: BEGIN-cascade blocks application
Date: Fri, 02 Apr 2004 12:32:04 METDST
Message-ID: <200404021032.MAA07447@rodos> (raw)
It's
PostgreSQL 7.3.4 on hppa-hp-hpux10.20, compiled by GCC 2.8.1
I'm having a ported monitoring application using the libpq interface.
After running well for several hours it surprisingly stopped
without any error condition.
The application was blocked completely.
After re-start it worked as expected.
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 eliminated those duplicates and now the
application runs without any stops.
Was it my fault?
From reading the manual I was not aware firing duplicate BEGINs
(ok, there were probably several thousand, but not uncommitted)
could have such an drastic effect.
Regards, Christoph
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: ch@rodos.fzk.de
Subject: Re: BEGIN-cascade blocks application
In-Reply-To: <200404021032.MAA07447@rodos>
* 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