Re: [PATCHES] VACUUM Improvements - WIP Patch - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: [PATCHES] VACUUM Improvements - WIP Patch
Date
Msg-id 487C5E96.1020907@enterprisedb.com
Whole thread Raw
In response to Re: [PATCHES] VACUUM Improvements - WIP Patch  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Gregory Stark wrote:
> I thought
> we only pruned when we wanted to insert a new tuple and found not enough
> space.

Nope, we prune on any access to the page, if the page is "full enough", 
and the pd_prune_xid field suggests that there is something to prune.

The problem with only pruning on inserts is that by the time we get to 
heap_insert/heap_update, we're already holding a pin on the page, which 
prevents us from acquiring the vacuum lock.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: ITAGAKI Takahiro
Date:
Subject: Re: [PATCHES] WIP: executor_hook for pg_stat_statements
Next
From: Simon Riggs
Date:
Subject: Re: [PATCHES] WIP: executor_hook for pg_stat_statements