Re: race condition in pg_class

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: 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-16 23:01:01
Message-ID: Zm9ura4-QHacn9mx@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jun 16, 2024 at 07:07:08AM -0700, Noah Misch wrote:
> It would be odd to detect exactly 0x0B000000U and not other invalid inputs,
> like 0x0A000001U where only 0x0B000001U is valid. I'm attaching roughly what
> it would take. Shall I squash this into inplace031?

Agreed that merging both together is cleaner. Moving the event class
into the key of WaitEventCustomEntryByInfo leads to a more consistent
final result.

> The thing I feel strongly about here is keeping focus on fixing $SUBJECT bugs
> that are actually corrupting data out there.

Agreed to focus on that first.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-06-16 23:07:49 Re: Using LibPq in TAP tests via FFI
Previous Message Thomas Munro 2024-06-16 22:57:35 Re: Using LibPq in TAP tests via FFI