From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, "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: | Add support for INDEX_CLEANUP and TRUNCATE to vacuumdb |
Date: | 2020-06-11 00:41:17 |
Message-ID: | 6F7F17EF-B1F2-4681-8D03-BA96365717C0@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi hackers,
I quickly put together a patch to add INDEX_CLEANUP and TRUNCATE to
vacuumdb before noticing a previous thread for it [0]. My take on it
was to just name the options --skip-index-cleanup and --skip-truncate.
While that does not give you a direct mapping to the corresponding
VACUUM options, it simplifies the patch by avoiding the boolean
parameter parsing stuff altogether.
Nathan
[0] https://postgr.es/m/CAHGQGwENx3Kvxq0U%2BwkGAdoAd89iaaWo_Pd5LBPUO4AqqhgyYQ%40mail.gmail.com
Attachment | Content-Type | Size |
---|---|---|
v1-0001-Add-skip-index-cleanup-and-skip-truncate-to-vacuu.patch | application/octet-stream | 8.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Melanie Plageman | 2020-06-11 00:48:17 | Re: Default setting for enable_hashagg_disk |
Previous Message | Tom Lane | 2020-06-10 22:02:20 | Re: Recording test runtimes with the buildfarm |