Re: Random pg_upgrade 004_subscription test failure on drongo - Mailing list pgsql-hackers

From vignesh C
Subject Re: Random pg_upgrade 004_subscription test failure on drongo
Date
Msg-id CALDaNm2LzW9iQB1=Q5PhMUvhzvYFeGkJFO+3tD8+r6bKS3whoA@mail.gmail.com
Whole thread Raw
In response to Re: Random pg_upgrade 004_subscription test failure on drongo  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On Thu, 13 Mar 2025 at 18:10, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
>
> Hmm, this problem isn't limited to this one pg_upgrade test, right? It
> could happen with any pg_upgrade invocation. And perhaps in a running
> server too, if a relfilenumber is reused quickly.

Yes, it can happen with these scenarios.

> In dropdb() and DropTableSpace() we do this:
>
> WaitForProcSignalBarrier(EmitProcSignalBarrier(PROCSIGNAL_BARRIER_SMGRRELEASE));
>
> Should we do the same here? Not sure where exactly to put that; perhaps
> in mdcreate(), if the creation fails with STATUS_DELETE_PENDING.

I felt mdcreate would be a good place to fix this issue.

Regards,
Vignesh



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Fix couple of typos
Next
From: Michael Paquier
Date:
Subject: Re: Add Pipelining support in psql