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

From Masahiko Sawada
Subject Re: Reviewing freeze map code
Date
Msg-id CAD21AoCyz5hmm4KwpWd23CUHaDPua7mBYzMh_3F=kPkbkn-A6g@mail.gmail.com
Whole thread Raw
In response to Re: Reviewing freeze map code  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On Tue, May 17, 2016 at 4:34 PM, Joshua D. Drake <jd@commandprompt.com> wrote:
> On 05/17/2016 12:32 PM, Alvaro Herrera wrote:
>
>>   Syntaxes are;
>>   VACUUM (SCAN_ALL) table_name;
>>   VACUUM (SCAN_ALL);  -- for all tables on database
>>
>> 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).  How about COMPLETE, TOTAL, or WHOLE?
>>
>
> VACUUM (ANALYZE, VERBOSE, WHOLE)
> ....
>
> That seems reasonable? I agree that SCAN_ALL doesn't fit. I am not trying to
> pull a left turn but is there a technical reason we don't just make FULL do
> this?
>

FULL option requires AccessExclusiveLock, which could be a problem.

Regards,

--
Masahiko Sawada



pgsql-hackers by date:

Previous
From: Shay Rojansky
Date:
Subject: Re: Parameters don't work in FETCH NEXT clause?
Next
From: Vik Fearing
Date:
Subject: Re: Reviewing freeze map code