Re: confusion about this commit "Revert "Skip redundant anti-wraparound vacuums""

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: jiye <jiye_sw(at)126(dot)com>
Cc: "robertmhaas(at)gmail(dot)com" <robertmhaas(at)gmail(dot)com>, "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: confusion about this commit "Revert "Skip redundant anti-wraparound vacuums""
Date: 2023-06-07 07:48:52
Message-ID: 20230607074852.ivhkx3wqhbg7dtvi@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 07, 2023 at 03:42:25PM +0800, jiye wrote:
> we will update all commits with latest version certaintly, but we must
> confirm that this issue is same with it currently we can not confirm this
> issue can be fixed by revert 2aa6e331ead7f3ad080561495ad4bd3bc7cd8913 this
> commit, so i just query about how this commit can trigger autovacuum lock
> down or does not work.

The revert commit contains a description of the problem and a link to the
discussion and analysis that led to that revert.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2023-06-07 08:00:00 Re: Importing pg_bsd_indent into our source tree
Previous Message jiye 2023-06-07 07:42:25 Re: confusion about this commit "Revert "Skip redundant anti-wraparound vacuums""