Re: race condition in pg_class

From: Noah Misch <noah(at)leadboat(dot)com>
To: Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Smolkin Grigory <smallkeen(at)gmail(dot)com>
Subject: Re: race condition in pg_class
Date: 2024-06-13 20:22:23
Message-ID: 20240613202223.11.nmisch@google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 12, 2024 at 10:02:00PM +0200, Michail Nikolaev wrote:
> > Can you say more about the connection you see between $SUBJECT and that?
> That
> > looks like a valid report of an important bug, but I'm not following the
> > potential relationship to $SUBJECT.
>
> I was guided by the following logic:
> * A pg_class race condition can cause table indexes to look stale.
> * REINDEX updates indexes
> * errors can be explained by different backends using different arbiter
> indexes

Got it. The race condition of $SUBJECT involves inplace updates, and the
wrong content becomes permanent. Hence, I suspect they're unrelated.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-06-13 20:27:35 Re: RFC: adding pytest as a supported test framework
Previous Message Andrew Dunstan 2024-06-13 20:19:21 Re: RFC: adding pytest as a supported test framework