Re: Add support for INDEX_CLEANUP and TRUNCATE to vacuumdb

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
Cc: Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "masao(dot)fujii(at)gmail(dot)com" <masao(dot)fujii(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "euler(at)timbira(dot)com(dot)br" <euler(at)timbira(dot)com(dot)br>
Subject: Re: Add support for INDEX_CLEANUP and TRUNCATE to vacuumdb
Date: 2020-06-19 01:57:01
Message-ID: 20200619015701.GD453547@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 18, 2020 at 09:26:50PM +0000, Bossart, Nathan wrote:
> It looks like I missed a couple of tags in the documentation changes.
> That should be fixed in v3.

Thanks. This flavor looks good to me in terms of code, and the test
coverage is what's needed for all the code paths added. This version
is using my suggestion of upthread for the option names: --no-truncate
and --no-index-cleanup. Are people fine with this choice?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2020-06-19 02:02:29 Re: Missing HashAgg EXPLAIN ANALYZE details for parallel plans
Previous Message Michael Paquier 2020-06-19 01:39:58 Re: min_safe_lsn column in pg_replication_slots view