Re: VACUUMs and WAL - Mailing list pgsql-hackers

From Tom Lane
Subject Re: VACUUMs and WAL
Date
Msg-id 18666.1225197734@sss.pgh.pa.us
Whole thread Raw
In response to VACUUMs and WAL  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> Looking at a VACUUM's WAL records makes me think twice about the way we
> issue a VACUUM.

> 1. First we scan the heap, issuing a HEAP2 clean record for every block
> that needs cleaning.

> 2. Then we scan the index, issuing WAL records as appropriate.

> 3. Then we rescan the heap, issuing a HEAP2 clean record for every
> block.

The first pass removes dead HOT tuples.  The second pass removes dead
normal tuples (it does NOT write "every block", only those with dead
tuples).  In principle the set of pages written in pass 1 might be
completely disjoint from the set of pages written in pass 2 (though
I admit that's probably not real likely).

> Surely we can come up with a better plan than that one?

Maybe, but it's not as bad as you're painting it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: VACUUMs and WAL
Next
From: Heikki Linnakangas
Date:
Subject: Re: Proposal of PITR performance improvement for 8.4.