Re: vacuumdb and new VACUUM options

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: vacuumdb and new VACUUM options
Date: 2019-05-18 10:18:38
Message-ID: 20190518101838.GC19212@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 17, 2019 at 01:11:53PM -0700, Andres Freund wrote:
> My impression is that these are better treated as feature work, to be
> tackled in v13. I see no urgency to push this for v12. There's still
> some disagreements on how parts of this are implemented, and we've beta1
> coming up.

It is true that we have lived without some options in vacuumdb while
these were already introduced at the SQL level, so I am in favor of
what you suggest here. Fujii-san, what do you think?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2019-05-18 10:48:35 Re: Multivariate MCV stats can leak data to unprivileged users
Previous Message Dean Rasheed 2019-05-18 09:11:58 Re: Multivariate MCV stats can leak data to unprivileged users