| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Gurjeet Singh <gurjeet(at)singh(dot)im>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org>, Will Storey <will(at)summercat(dot)com> |
| Subject: | Re: Disabling vacuum truncate for autovacuum |
| Date: | 2025-02-28 06:19:32 |
| Message-ID: | 97160e4b549c726bd409c8059a1bfaf07e7a6d04.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, 2025-02-27 at 21:35 -0600, Nathan Bossart wrote:
> I spent some time on this one today. A couple of notes:
>
> * Since the reloption is a Boolean, there isn't a good way to tell whether
> it is actually set for the table or if it just inherited the default
> value. This is important to know because we want the reloption to
> override the GUC.
I agree with that, without being able to think of a better solution.
> * I didn't see a good GUC category for vacuum_truncate. I suppose we could
> create a new one, but for now I've just stashed it into the autovacuum
> one. Bikeshedding welcome.
Why not use "Client Connection Defaults / Statement Behavior", just like for
"vacuum_freeze_min_age"? I don't think that "autovacuum" is appropriate,
since it applies to manual VACUUM as well.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KK CHN | 2025-02-28 11:51:50 | Long Running query and trace potential issues |
| Previous Message | Gurjeet Singh | 2025-02-28 04:29:16 | Re: Disabling vacuum truncate for autovacuum |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhishek Chanda | 2025-02-28 06:20:17 | Re: Adding support for SSLKEYLOGFILE in the frontend |
| Previous Message | Sagar Shedge | 2025-02-28 06:10:39 | Re: Extend postgres_fdw_get_connections to return remote backend pid |