Re: Reviewing freeze map code
От | Masahiko Sawada |
---|---|
Тема | Re: Reviewing freeze map code |
Дата | |
Msg-id | CAD21AoBuNs7kBp=EAhFHEmffy6SaCZ0Bfsux3hAdp9n90abmVA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Reviewing freeze map code (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Reviewing freeze map code
|
Список | pgsql-hackers |
On Mon, May 16, 2016 at 10:49 AM, Robert Haas <robertmhaas@gmail.com> wrote: > On Tue, May 10, 2016 at 10:40 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote: >> Or second way I came up with is having tool to remove particular _vm >> file safely, which is executed via SQL or client tool like >> pg_resetxlog. >> >> Attached updated VACUUM SCAN_ALL patch. >> Please find it. > > We should support scan_all only with the new-style options syntax for > VACUUM; that is, vacuum (scan_all) rename. That doesn't require > making scan_all a keyword, which is good: this is a minor feature, and > we don't want to bloat the parsing tables for it. > I agree with having new-style options syntax. Isn't it better to have SCAN_ALL option without parentheses? Syntaxes are; VACUUM SCAN_ALL table_name; VACUUM SCAN_ALL; -- for all tables on database Regards, -- Masahiko Sawada
В списке pgsql-hackers по дате отправления: