Re: Reviewing freeze map code
От | Robert Haas |
---|---|
Тема | Re: Reviewing freeze map code |
Дата | |
Msg-id | CA+TgmoadhUj=vr44qPZU13F6R3eGAc637Lh6EO3CnXoxOrhV1Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Reviewing freeze map code (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
Re: Reviewing freeze map code
|
Список | pgsql-hackers |
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. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: