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

From Jeff Janes
Subject Re: Reviewing freeze map code
Date
Msg-id CAMkU=1ygHztvjr-hS3RRLyYmEdZkTDrwf5Cjch4xa5HLcpZRDQ@mail.gmail.com
Whole thread Raw
In response to Re: Reviewing freeze map code  (Joe Conway <mail@joeconway.com>)
Responses Re: Reviewing freeze map code  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Wed, May 18, 2016 at 7:09 AM, Joe Conway <mail@joeconway.com> wrote:
> On 05/18/2016 09:55 AM, Victor Yegorov wrote:
>> 2016-05-18 16:45 GMT+03:00 Robert Haas <robertmhaas@gmail.com
>> <mailto:robertmhaas@gmail.com>>:
>>
>>     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.
>>
>>
>> VACUUM (INCLUDING ALL) ?
>
> VACUUM (FORCE ALL) ?


How about going with something that says more about why we are doing
it, rather than trying to describe in one or two words what it is
doing?

VACUUM (FORENSIC)

VACUUM (DEBUG)

VACUUM (LINT)

Cheers,

Jeff



pgsql-hackers by date:

Previous
From: chang chao
Date:
Subject: Re: The rewritting of join conditions caused a very slow query plan.
Next
From: chang chao
Date:
Subject: explain analyze does not report actual rows correctly?