Re: Reviewing freeze map code - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Reviewing freeze map code
Date
Msg-id CA+TgmoYE6wCKpoxnoJfqizpi-zTYHvjgN0YWR-hPzbZDWR_m6w@mail.gmail.com
Whole thread Raw
In response to Re: Reviewing freeze map code  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Reviewing freeze map code
List pgsql-hackers
On Wed, May 18, 2016 at 9:42 AM, Joshua D. Drake <jd@commandprompt.com> wrote:
>> It's not a bad thought, but I do think it might be a bit confusing.
>> My main priority for this new option is that people aren't tempted to
>> use it very often, and I think a name like "even_frozen_pages" is more
>> likely to accomplish that than just "frozen".
>
> freeze_all_pages?

No, that's what the existing FREEZE option does.  This new option is
about unnecessarily vacuuming pages that don't need it.  The
expectation is that vacuuming all-frozen pages will be a no-op.

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



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Reviewing freeze map code
Next
From: Simon Riggs
Date:
Subject: Re: memory layouts for binary search in nbtree