Re: Reviewing freeze map code

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>
Cc: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, Vik Fearing <vik(at)2ndquadrant(dot)fr>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>, Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reviewing freeze map code
Date: 2016-05-18 13:42:37
Message-ID: 573C714D.2060505@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/18/2016 05:51 AM, Robert Haas wrote:
> On Wed, May 18, 2016 at 8:41 AM, David Steele <david(at)pgmasters(dot)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".
>

freeze_all_pages?

JD

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-05-18 13:45:03 Re: Reviewing freeze map code
Previous Message Andres Freund 2016-05-18 13:25:37 memory layouts for binary search in nbtree