autovacuum default run with vacuum_index_cleanup and vacuum_truncate and related lock? - Mailing list pgsql-admin

From James Pang (chaolpan)
Subject autovacuum default run with vacuum_index_cleanup and vacuum_truncate and related lock?
Date
Msg-id PH0PR11MB51917B6D0E1C97DA6EAAEC3FD62C9@PH0PR11MB5191.namprd11.prod.outlook.com
Whole thread Raw
Responses Re: autovacuum default run with vacuum_index_cleanup and vacuum_truncate and related lock?  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-admin

Hi,

It’s Postgres 13 version, we plan to migrate from Oracle to Postgres 13 on RHEL8.  One maintain job is about autovacuum, with default config,  autovacuum will do on tables with  “vacuum_index_cleanup” and “vacuum_truncate” option?   With both options, autovacuum woker will hold “access exclusive” lock when truncate empty blocks and cleanup index ?  if that’s true, how to handle autovacuum to reduce the lock blocking issue?

 

Thanks,

 

James

pgsql-admin by date:

Previous
From: Goti
Date:
Subject: Re: Does aurora PostgreSQL use wal_buffers?
Next
From: "James Pang (chaolpan)"
Date:
Subject: Disk IO wait event DataFileImmediateSync and DataFileSync