Re: New vacuum option to do only freezing - Mailing list pgsql-hackers

From Robert Haas
Subject Re: New vacuum option to do only freezing
Date
Msg-id CA+Tgmoa4zSzCtefreLY1L+39=BavY=LZfydd9tdTzXsH3MJZzw@mail.gmail.com
Whole thread Raw
In response to Re: New vacuum option to do only freezing  (Andres Freund <andres@anarazel.de>)
Responses Re: New vacuum option to do only freezing  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Wed, May 1, 2019 at 12:14 PM Andres Freund <andres@anarazel.de> wrote:
> On 2019-04-06 16:13:53 +0900, Michael Paquier wrote:
> > On Sat, Apr 06, 2019 at 11:31:31AM +0900, Masahiko Sawada wrote:
> > > Yes, but Fujii-san pointed out that this option doesn't support toast
> > > tables and I think there is not specific reason why not supporting
> > > them. So it might be good to add toast.vacuum_index_cleanup. Attached
> > > patch.
> >
> > Being able to control that option at toast level sounds sensible.  I
> > have added an open item about that.
>
> Robert, what is your stance on this open item? It's been an open item
> for about three weeks, without any progress.

The actual bug in this patch needs to be fixed, but I see we have
another open item for that.  This open item, as I understand it, is
all about whether we should add another reloption so that you can
control this behavior separately for TOAST tables.  In my opinion,
that's not a critical change and the open item should be dropped, but
others might see it differently.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: using index or check in ALTER TABLE SET NOT NULL
Next
From: Tomas Vondra
Date:
Subject: Re: walsender vs. XLogBackgroundFlush during shutdown