Re: Vaccuming dead rows on busy databases - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Vaccuming dead rows on busy databases
Date
Msg-id 27321.1166468055@sss.pgh.pa.us
Whole thread Raw
In response to Vaccuming dead rows on busy databases  ("Greg Sabino Mullane" <greg@turnstep.com>)
Responses Re: Vaccuming dead rows on busy databases  (Matthew O'Connor <matthew@zeut.net>)
Re: Vaccuming dead rows on busy databases  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-hackers
"Greg Sabino Mullane" <greg@turnstep.com> writes:
> I'd like to see something like VACUUM FULL WAIT. :)

Sounds like a deadlock waiting to happen :-(

AFAIK the general practice is to just accept the fact that vacuum can't
remove recently-dead tuples.  You should look into whether you can't
shorten your transactions --- very-long-running transactions create
other performance issues besides vacuum not removing stuff.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Greg Sabino Mullane"
Date:
Subject: Vaccuming dead rows on busy databases
Next
From: Matthew O'Connor
Date:
Subject: Re: Vaccuming dead rows on busy databases