public inbox for [email protected]
help / color / mirror / Atom feedFrom: jiye <[email protected]>
To: [email protected] <[email protected]>
Subject: confusion about this commit "Revert "Skip redundant anti-wraparound vacuums""
Date: Mon, 5 Jun 2023 11:30:48 +0800 (GMT+08:00)
Message-ID: <[email protected]> (raw)
hi,
in our test enviroment, if one database's have major update operations, autovacuum does not work and cause major performance degradation.
if found this issue may be resolved by revert this Skip redundant anti-wraparound vacuums ยท postgres/postgres@2aa6e33 (github.com) commit.
after fetch some disccusion about this revert, i have some question as follow:
1. i understand that anti-wraparound and no-aggressive autovacuum will be skipped for shared catalog tables, but why this can trigger autovacuum does not work for others tables ?
2. "this could cause autovacuum to lock down", this lock down implict that autovacuum can make a dead lock problem ?
3. how to reproduce this lock down or autovacuum invalid issue, must be cluster enviroment ?
so is there any body know these issuse or commits can give me some suggestion about my confusion.
| |
jiye
|
|
[email protected]
|
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: confusion about this commit "Revert "Skip redundant anti-wraparound vacuums""
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox