Re: [PERFORM] vacuum'ing toast crumbs, detecting dangling transactions

2009-11-04 Thread Scott Marlowe
On Wed, Nov 4, 2009 at 2:18 PM, Dave Crooke 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

Re: [PERFORM] vacuum'ing toast crumbs, detecting dangling transactions

2009-11-04 Thread Kevin Grittner
Dave Crooke wrote: > I'm not defending the decision to store blobs in a database (it was > taken a while ago, before the need for frequent updates of the XML) > and it isn't something that can be readily changed at short notice, > so please no advice about "don't do that" :-) I wouldn't sweat

[PERFORM] vacuum'ing toast crumbs, detecting dangling transactions

2009-11-04 Thread Dave Crooke
Hi folks I had a couple of semi-newbie questions about this, which I couldn't find obvious answers to in the archives ... we are using Postgres 8.3, and the behaviour is the same across Windows and Linux. I am working with an app which, among other things stores XML files (average about 50KB in s