| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Cc: | Robert Treat <rob(at)xzilla(dot)net>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Gurjeet Singh <gurjeet(at)singh(dot)im>, Andres Freund <andres(at)anarazel(dot)de>, Will Storey <will(at)summercat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Disabling vacuum truncate for autovacuum |
| Date: | 2025-03-19 15:40:31 |
| Message-ID: | Z9rlb0jgNLm8ULAB@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, Mar 20, 2025 at 12:34:59AM +0900, Fujii Masao wrote:
> +# - Default Behavior -
> +
> +#vacuum_truncate = on # enable truncation after vacuum
>
> Since there's no existing GUC category that fits to vacuum_truncate,
> I'm fine with adding a new category like "Vacuuming" and placing
> vacuum_truncate there.
>
> However, if we do this, ISTM that the new category should also be added to
> guc_tables.h, and vacuum_truncate should be assigned to it in guc_tables.c.
> Additionally, the documentation should be updated to include
> the new category, with vacuum_truncate placed under it. Thought?
Ah, you're right, I need to fix the category. Will post an updated patch
soon.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-03-19 16:09:21 | Re: Disabling vacuum truncate for autovacuum |
| Previous Message | Fujii Masao | 2025-03-19 15:34:59 | Re: Disabling vacuum truncate for autovacuum |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-03-19 15:41:59 | Re: optimize file transfer in pg_upgrade |
| Previous Message | Sami Imseih | 2025-03-19 15:38:26 | Re: making EXPLAIN extensible |