Re: Add MAIN_RELATION_CLEANUP and SECONDARY_RELATION_CLEANUP options to VACUUM - Mailing list pgsql-hackers

From Bossart, Nathan
Subject Re: Add MAIN_RELATION_CLEANUP and SECONDARY_RELATION_CLEANUP options to VACUUM
Date
Msg-id 855FB31E-5616-4910-BFF2-ABFE24716F50@amazon.com
Whole thread Raw
In response to Re: Add MAIN_RELATION_CLEANUP and SECONDARY_RELATION_CLEANUP options to VACUUM  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Add MAIN_RELATION_CLEANUP and SECONDARY_RELATION_CLEANUP options to VACUUM  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 1/28/21, 11:15 PM, "Michael Paquier" <michael@paquier.xyz> wrote:
> On Thu, Jan 28, 2021 at 06:16:09PM +0000, Bossart, Nathan wrote:
>> I chose TOAST_TABLE_CLEANUP to match the INDEX_CLEANUP option, but I'm
>> not wedded to that name.  What do you think about PROCESS_TOAST_TABLE?
>
> Most of the other options use a verb, so using PROCESS, or even SKIP
> sounds like a good idea.  More ideas: PROCESS_TOAST, SKIP_TOAST.  I
> don't like much the term CLEANUP here, as it may imply, at least to
> me, that the toast relation is getting partially processed.

I changed it to PROCESS_TOAST.

> +       <para>
> +        Do not clean up the TOAST table.
> +       </para>
> Is that enough?  I would say instead: "Skip the TOAST table associated
> to the table to vacuum, if any."

Done.

Nathan


Attachment

pgsql-hackers by date:

Previous
From: Alexey Kondratov
Date:
Subject: Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly
Next
From: Fujii Masao
Date:
Subject: Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit