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

From Gavin Flower
Subject Re: Reviewing freeze map code
Date
Msg-id 142e516d-2b66-1859-6733-aabd6ab9a272@archidevsys.co.nz
Whole thread Raw
In response to Re: Reviewing freeze map code  (Vik Fearing <vik@2ndquadrant.fr>)
Responses Re: Reviewing freeze map code  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 18/05/16 09:34, Vik Fearing wrote:
> On 17/05/16 21:32, Alvaro Herrera wrote:
>> Is SCAN_ALL really the best we can do here?  The business of having an
>> underscore in an option name has no precedent (other than
>> CURRENT_DATABASE and the like).
> ALTER DATABASE has options for ALLOW_CONNECTIONS, CONNECTION_LIMIT, and
> IS_TEMPLATE.
>
>> How about COMPLETE, TOTAL, or WHOLE?
> Sure, I'll play this game.  I like EXHAUSTIVE.

I prefer 'WHOLE', as it seems more obvious (and not because of the pun 
relating to 'wholesomeness'!!!)




pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: seg fault in contrib/bloom
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Allocate all page images at once in generic wal interface