autovacuum default run with vacuum_index_cleanup and vacuum_truncate and related lock?

From: "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com>
To: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: autovacuum default run with vacuum_index_cleanup and vacuum_truncate and related lock?
Date: 2022-02-07 08:43:39
Message-ID: PH0PR11MB51917B6D0E1C97DA6EAAEC3FD62C9@PH0PR11MB5191.namprd11.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message James Pang (chaolpan) 2022-02-07 08:46:27 Disk IO wait event DataFileImmediateSync and DataFileSync
Previous Message Goti 2022-02-07 03:35:32 Re: Does aurora PostgreSQL use wal_buffers?