Re: optimizing vacuum truncation scans

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: optimizing vacuum truncation scans
Date: 2015-07-23 15:09:41
Message-ID: 20150723150941.GE21169@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-07-23 11:06:25 -0400, Robert Haas wrote:
> I don't know what to do about the fact that it loses to the VM-bit
> based approach, but I think it's a bad bet that we will never care
> about setting visibility map bits anyplace other than VACUUM.

+1

A background process that tries to hint all pages shortly before they're
written out would be truly awesome. And would very likely set hint
bits...

Andres

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-07-23 15:19:52 Re: Eliminating CREATE INDEX comparator TID tie-breaker overhead
Previous Message Robert Haas 2015-07-23 15:06:25 Re: optimizing vacuum truncation scans