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-22 04:35:18
Message-ID: 20200622043518.GD5367@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 19, 2020 at 10:57:01AM +0900, Michael Paquier wrote:
> 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?

Okay. I have gone through the patch again, and applied it as of
9550ea3. Thanks.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-06-22 04:48:11 Re: tag typos in "catalog.sgml"
Previous Message Pavel Stehule 2020-06-22 03:48:48 proposal: unescape_text function