| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch>, Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: AW: [Extern] Re: autovacuum on pg_catalog tables |
| Date: | 2021-06-04 16:04:31 |
| Message-ID: | d0695f9d08ee0b783753040232f02ffc85b7cf37.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2021-06-04 at 15:43 +0000, Zwettler Markus (OIZ) wrote:
> I have a lot of LO manipulation and want a more aggressive autovacuum on some pg_catalog tables therefore.
>
> I do not see any reason why this should not work or be at risk?
It is not a risk per se. The biggest problem is that any such catalog
modifications would be lost after an upgrade.
I would change the parameters in "postgresql.conf" and then override the
settings for user table to be less aggressive where necessary.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atul Kumar | 2021-06-04 16:06:49 | Re: strange behavior of WAL files |
| Previous Message | Tom Lane | 2021-06-04 16:03:05 | Re: AW: [Extern] Re: autovacuum on pg_catalog tables |