Re: vacuum'ing toast crumbs, detecting dangling transactions - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: vacuum'ing toast crumbs, detecting dangling transactions
Date
Msg-id dcc563d10911041351j5c4e0a85oa62889acd58b6376@mail.gmail.com
Whole thread Raw
In response to vacuum'ing toast crumbs, detecting dangling transactions  (Dave Crooke <dcrooke@gmail.com>)
List pgsql-performance
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.

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: vacuum'ing toast crumbs, detecting dangling transactions
Next
From: Dave Crooke
Date:
Subject: Followup: vacuum'ing toast