Skip site navigation (1) Skip section navigation (2)

Re: max_fsm_pages question

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Michael Monnerie" <michael(dot)monnerie(at)is(dot)it-management(dot)at>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: max_fsm_pages question
Date: 2010-01-25 16:28:23
Message-ID: 4B5D7247020000250002EB70@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at> wrote:
 
> such a bloat can't happen in a day.
 
That is evidence that you may have a problem with some long-running
transaction which stays open for days, possibly "idle in
transaction".  Bloat will accumulate, without any vacuum being able
to prevent it or recover from it, until the transaction terminates.
It will not show up as free space in your vacuum verbose output
while the transaction remains open; although I believe it will show
up in the "dead row versions cannot be removed yet" count.
 
> Finding out which table the toast belongs to would be great, maybe
> that helps further investigation.
 
Have a look at reltoastrelid:
 
http://www.postgresql.org/docs/8.3/interactive/catalog-pg-class.html
 
-Kevin

In response to

Responses

pgsql-admin by date

Next:From: Michael MonnerieDate: 2010-01-25 16:37:05
Subject: Re: max_fsm_pages question
Previous:From: Kenneth MarshallDate: 2010-01-25 15:38:21
Subject: Re: how to speed ilike

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group