Re: vacuum'ing toast crumbs, detecting dangling transactions

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Dave Crooke" <dcrooke(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: vacuum'ing toast crumbs, detecting dangling transactions
Date: 2009-11-04 21:30:25
Message-ID: 4AF19E11020000250002C2B0@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Dave Crooke <dcrooke(at)gmail(dot)com> 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 50kB chunks of XML. We store 10MB PDF files. :-)

> is showing 40-50% dead tuples. However, if I disconnect the app, all
> the dead tuples clean up and moved to the "free space" category.

As you suspected, that sounds like lingering database transactions.
Try looking at the pg_stat_activity table for transactions "IDLE in
transaction". If you're having trouble pinning down the cause, look
the pg_locks view to see what tables they've been in.

-Kevin

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2009-11-04 21:51:57 Re: vacuum'ing toast crumbs, detecting dangling transactions
Previous Message Dave Crooke 2009-11-04 21:18:46 vacuum'ing toast crumbs, detecting dangling transactions