| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: VACUUM (DISABLE_PAGE_SKIPPING on) |
| Date: | 2020-11-20 15:33:40 |
| Message-ID: | 20201120153340.GA26873@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Nov-20, Simon Riggs wrote:
> On Fri, 20 Nov 2020 at 01:40, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> > Since we use the term aggressive scan in the docs, I personally don't
> > feel unnatural about that. But since this option also disables index
> > cleanup when not enabled explicitly, I’m concerned a bit if user might
> > get confused. I came up with some names like FEEZE_FAST and
> > FREEZE_MINIMAL but I'm not sure these are better.
>
> FREEZE_FAST seems good.
VACUUM (CHILL) ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-11-20 15:38:55 | Re: VACUUM (DISABLE_PAGE_SKIPPING on) |
| Previous Message | Alvaro Herrera | 2020-11-20 15:29:44 | Re: VACUUM (DISABLE_PAGE_SKIPPING on) |