| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Cc: | Gurjeet Singh <gurjeet(at)singh(dot)im>, Robert Haas <robertmhaas(at)gmail(dot)com>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org>, Will Storey <will(at)summercat(dot)com> |
| Subject: | Re: Disabling vacuum truncate for autovacuum |
| Date: | 2025-03-14 21:01:09 |
| Message-ID: | e9f3d991b8820fd1e076367b20709a1be2558227.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Fri, 2025-03-14 at 10:42 -0500, Nathan Bossart wrote:
> One other difference in my version of the patch [0] is to call this GUC
> vacuum_truncate and have it apply to both autovacuum and VACUUM.
I agree that that is the way to go.
It makes no sense to restrict the feature to autovacuum.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2025-03-15 13:59:59 | Re: Disabling vacuum truncate for autovacuum |
| Previous Message | Nathan Bossart | 2025-03-14 15:42:07 | Re: Disabling vacuum truncate for autovacuum |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-03-14 21:13:52 | Re: PG_CFLAGS rpath Passthrough Issue |
| Previous Message | Tom Lane | 2025-03-14 20:52:26 | Re: SQLFunctionCache and generic plans |