Postgres Pro
Downloads
Home   >   mailing lists

Re: Set visibility map bit after HOT prune - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Set visibility map bit after HOT prune
Date
Msg-id CA+Tgmoa5XAbpOtbd1_wgaH8vC0T145VyXtspeLgxdCiWR0B60Q@mail.gmail.com
Whole thread Raw
In response to Re: Set visibility map bit after HOT prune  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Set visibility map bit after HOT prune
Re: Set visibility map bit after HOT prune
List pgsql-hackers
Tree view 
On Wed, Dec 19, 2012 at 12:39 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> The benefit of saying that only UPDATEs clean the block is that this
> penalises only the workload making the mess, rather than everybody
> cleaning up repeatedly over one messy guy.

Right, but there are plenty of situations where having everybody clean
up after the messy guy is better than waiting around and hoping that
Mom (aka vacuum) will do it.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Set visibility map bit after HOT prune
Next
From: Tom Lane
Date:
Subject: operator dependency of commutator and negator, redux