From: Scott Marlowe <scott.marlowe@gmail.com>
To: Dave Crooke <dcrooke@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: vacuum'ing toast crumbs, detecting dangling transactions
Date: Wed, 4 Nov 2009 14:51:57 -0700
Message-ID: <dcc563d10911041351j5c4e0a85oa62889acd58b6376@mail.gmail.com> (raw)
In-Reply-To: <ca24673e0911041318p1c05c009l95c13b74dcb93b3@mail.gmail.com>
References: <ca24673e0911041318p1c05c009l95c13b74dcb93b3@mail.gmail.com>
On Wed, Nov 4, 2009 at 2:18 PM, Dave Crooke <dcrooke@gmail.com> wrote:
> 2. If there is a hanging transaction, what's the best way to trace it from
> the PG end? Client is classic Java (Spring / Hibernate / Apache DBCP) if
> that matters.
Last place I worked we had the same issue and it was in our jdbc
settings or maybe needed an upgraded version. It was some slick trick
someone thought of to do a commit;begin; at the end of each access to
the db. It's that begin; that gets in the way, especially if there's
an occasional select 1 to make sure the connection is alive.
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-performance@postgresql.org
Cc: scott.marlowe@gmail.com, dcrooke@gmail.com
Subject: Re: vacuum'ing toast crumbs, detecting dangling transactions
In-Reply-To: <dcc563d10911041351j5c4e0a85oa62889acd58b6376@mail.gmail.com>
* 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