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

From Robert Haas
Subject Re: Reviewing freeze map code
Date
Msg-id CA+TgmobZNDJGvKOM=qLzXqwZUdqowPKvG3gcp5WAMiypezOhig@mail.gmail.com
Whole thread Raw
In response to Re: Reviewing freeze map code  (David Steele <david@pgmasters.net>)
Responses Re: Reviewing freeze map code  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On Wed, May 18, 2016 at 8:41 AM, David Steele <david@pgmasters.net> wrote:
>> I think we should give this a name that hints more strongly at this
>> being an exceptional thing, like vacuum (even_frozen_pages).
>
> How about just FROZEN?  Perhaps it's too confusing to have that and FREEZE,
> but I thought I would throw it out there.

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".

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



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: Reviewing freeze map code
Next
From: Andres Freund
Date:
Subject: memory layouts for binary search in nbtree