Re: race condition in pg_class - Mailing list pgsql-hackers

From Noah Misch
Subject Re: race condition in pg_class
Date
Msg-id 20240614003549.c2.nmisch@google.com
Whole thread Raw
In response to Re: race condition in pg_class  (Noah Misch <noah@leadboat.com>)
Responses Re: race condition in pg_class
Re: race condition in pg_class
List pgsql-hackers
On Mon, Jun 10, 2024 at 07:45:25PM -0700, Noah Misch wrote:
> On Thu, Jun 06, 2024 at 09:48:51AM -0400, Robert Haas wrote:
> > It's not this patch set's fault, but I'm not very pleased to see that
> > the injection point wait events have been shoehorned into the
> > "Extension" category
> 
> I've replied on that branch of the thread.

I think the attached covers all comments to date.  I gave everything v3, but
most patches have just a no-conflict rebase vs. v2.  The exceptions are
inplace031-inj-wait-event (implements the holding from that branch of the
thread) and inplace050-tests-inj (updated to cooperate with inplace031).  Much
of inplace031-inj-wait-event is essentially s/Extension/Custom/ for the
infrastructure common to the two custom wait event types.

Thanks,
nm

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Revive num_dead_tuples column of pg_stat_progress_vacuum
Next
From: Tom Lane
Date:
Subject: Re: Revive num_dead_tuples column of pg_stat_progress_vacuum