| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reviewing freeze map code |
| Date: | 2016-05-16 14:49:13 |
| Message-ID: | CA+TgmoadhUj=vr44qPZU13F6R3eGAc637Lh6EO3CnXoxOrhV1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 10, 2016 at 10:40 PM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Palle Girgensohn | 2016-05-16 15:07:25 | pg_upgrade fails in 9.6 beta1 |
| Previous Message | Tom Lane | 2016-05-16 14:16:48 | Re: 10.0 |