Re: autovacuum doesnt run on the pg_toast_id table

I did it for the original table. But I see in the logs that the autovacuun
on the toasted table isn't synced with the autovacuun of the original
table. Therefore I thought that it worth to set it also for the toasted
table. Can you explain why in the logs I see more vacuums of the original
table then the toasted table ? Should they vacuumed together ?

On Jan 17, 2019 7:52 PM, "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com> wrote:

On 2019-Jan-17, Mariel Cherkassky wrote:

> I tried to set the same threshold for the toasted table but got an error
> that it is a catalog table and therefore permission is denied.
> 2019-01-17 12:04:15 EST db116109 ERROR: permission denied:
> "pg_toast_13388392" is a system catalog
> 2019-01-17 12:04:15 EST db116109 STATEMENT: alter table
> pg_toast.pg_toast_13388392 set (autovacuum_vacuum_scale_factor=0.05);

The right way to do this is
alter table main_table set (toast.autovacuum_vacuum_scale_factor = 0.05);

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services