On Fri, 21 Mar 2025 at 18:54, vignesh C <[email protected]> wrote: > > On Thu, 13 Mar 2025 at 18:10, Heikki Linnakangas <[email protected]> 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. 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. > > How about a patch similar to the attached one? I have run pg_upgrade > tests multiple times, but unfortunately, I was unable to reproduce the > issue or verify these changes.
CFBot reported an issue in one of the machines, here is an updated version for the same. Regards, Vignesh
v2-0001-Fix-issue-with-file-handle-retention-during-CREAT.patch
Description: Binary data
