Re: error "can only drop stats once" brings down database

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: florisvannee(at)optiver(dot)com, andres(at)anarazel(dot)de, bertranddrouvot(dot)pg(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: error "can only drop stats once" brings down database
Date: 2024-06-25 04:00:39
Message-ID: ZnpA5zqSgW2FfqYF@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jun 25, 2024 at 09:22:48AM +0900, Kyotaro Horiguchi wrote:
> Is it something like this? I forgot the reason why this was excluded
> from the vinal version, though.
>
> https://www.postgresql.org/message-id/20201001.090722.322196928507744460.horikyota.ntt%40gmail.com

That's a bit different than the gc_count presented in 0004, because
there is no relationship to autovacuum with the cleanup of the
entries, still there is some overlap in the thought process: this
suggestion just makes sure that any backend holding local references
to a shared entry with a different age does not attempt to manipulate
it after switching locally to a dropped state.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Antti Lampinen 2024-06-25 04:24:05 Re: BUG #18522: Wrong results with Merge Right Anti Join, inconsistent with Merge Anti Join
Previous Message Richard Guo 2024-06-25 02:07:31 Re: BUG #18522: Wrong results with Merge Right Anti Join, inconsistent with Merge Anti Join