Re: Reviewing freeze map code

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема Re: Reviewing freeze map code
Дата
Msg-id CAMkU=1ygHztvjr-hS3RRLyYmEdZkTDrwf5Cjch4xa5HLcpZRDQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Reviewing freeze map code  (Joe Conway <mail@joeconway.com>)
Ответы Re: Reviewing freeze map code  (Peter Geoghegan <pg@heroku.com>)
Список 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 по дате отправления:

Предыдущее
От: chang chao
Дата:
Сообщение: Re: The rewritting of join conditions caused a very slow query plan.
Следующее
От: chang chao
Дата:
Сообщение: explain analyze does not report actual rows correctly?