Re: vacuumdb and new VACUUM options - Mailing list pgsql-hackers

From Andres Freund
Subject Re: vacuumdb and new VACUUM options
Date
Msg-id 20190517201153.c4cn62deprey6dbv@alap3.anarazel.de
Whole thread Raw
In response to Re: vacuumdb and new VACUUM options  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: vacuumdb and new VACUUM options  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Hi,

On 2019-05-15 15:44:22 +0900, Masahiko Sawada wrote:
> From de60d212b50a6412e483c995b83e28c5597089ad Mon Sep 17 00:00:00 2001
> From: Masahiko Sawada <sawada.mshk@gmail.com>
> Date: Thu, 9 May 2019 20:02:05 +0900
> Subject: [PATCH v3 1/2] Add --index-cleanup option to vacuumdb.

> From 59e3146f585e288d41738daa9a1d18687e2851d1 Mon Sep 17 00:00:00 2001
> From: Masahiko Sawada <sawada.mshk@gmail.com>
> Date: Wed, 15 May 2019 15:27:51 +0900
> Subject: [PATCH v3 2/2] Add --truncate option to vacuumdb.
> 

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.

IMO we should just register this patch for the next CF, and drop the
open item.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Passing CopyMultiInsertInfo structure toCopyMultiInsertInfoNextFreeSlot()
Next
From: Andres Freund
Date:
Subject: Re: Multivariate MCV stats can leak data to unprivileged users