Re: vacuumdb and new VACUUM options

From: Andres Freund <andres(at)anarazel(dot)de>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, 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-17 20:11:53
Message-ID: 20190517201153.c4cn62deprey6dbv@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)mshk(at)gmail(dot)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(dot)mshk(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-05-17 20:29:38 Re: Multivariate MCV stats can leak data to unprivileged users
Previous Message Andres Freund 2019-05-17 20:04:30 Re: Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()