"Zwettler Markus (OIZ)" writes:
> I tried this on postgres 9.6:
> postgresql.conf -> allow_system_table_mods=on + pg_ctl restart
> # alter table pg_catalog.pg_shdepend set (autovacuum_vacuum_scale_factor = 0,
> autovacuum_vacuum_threshold = 1000);
> ERROR: shared tables cannot be toasted af
);
ERROR: AccessExclusiveLock required to add toast table.
Time: 1.601 ms
Any idea?
Thanks, Markus
Von: Zwettler Markus (OIZ)
Gesendet: Freitag, 4. Juni 2021 17:44
An: Vijaykumar Jain
Cc: pgsql-general@lists.postgresql.org
Betreff: AW: [Extern] Re: autovacuum on pg_catalog tables
Thanks
On Fri, 2021-06-04 at 15:43 +, 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
"Zwettler Markus (OIZ)" writes:
> I do not see any reason why this should not work or be at risk?
I think the only problem you'd be likely to run into is that
pg_dump/pg_upgrade won't propagate those settings for you.
autovacuum doesn't really treat catalogs differently from user
tables, AFAIR.
Thanks for the info.
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?
Markus
Von: Vijaykumar Jain
Gesendet: Freitag, 4. Juni 2021 17:37
An: Zwettler Markus (OIZ)
Cc: pg
