Re: Reviewing freeze map code
От | Alvaro Herrera |
---|---|
Тема | Re: Reviewing freeze map code |
Дата | |
Msg-id | 20160606141815.GA387566@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: Reviewing freeze map code (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Reviewing freeze map code
|
Список | pgsql-hackers |
Robert Haas wrote: > My gut feeling on this is to either do nothing or add a VACUUM option > (not a GUC, not a reloption) called even_frozen_pages, default false. > What is your opinion? +1 for that approach -- I thought that was already agreed weeks ago and the only question was what to name that option. even_frozen_pages sounds better than SCANALL, SCAN_ALL, FREEZE, FORCE (the other options I saw proposed in that subthread), so +1 for that naming too. I don't like doing nothing; that means that when we discover a bug we'll have to tell users to rm a file whose name requires a complicated catalog query to find out, so -1 for that. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: