Re: New vacuum option to do only freezing

From: Greg Stark <stark(at)mit(dot)edu>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New vacuum option to do only freezing
Date: 2018-11-06 02:12:30
Message-ID: CAM-w4HM1mV_KATdTVxY8hHtbgG-=GxZemDa2i3c+QT=weUqapw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon 5 Nov 2018, 12:49 Robert Haas <robertmhaas(at)gmail(dot)com wrote:

> That seems non-orthogonal. We have an existing flag to force freezing
> (FREEZE); we don't need a second option that does the same thing.
> Skipping the index scans (and thus necessarily the second heap pass)
> is a separate behavior which we don't currently have a way to control.
>

It sounds like it might be better to name this "VACUUM (FAST)” and document
that it skips some of the normal (and necessary) work that vacuum does and
is only suitable for avoiding wraparounds and not sufficient for avoiding
bloat

>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-11-06 02:19:25 Re: New vacuum option to do only freezing
Previous Message Thomas Munro 2018-11-06 02:10:42 Re: pread() and pwrite()