Re: Bug report - pg_upgrade tool seems to have a race condition when trying to delete a pg_wal file

On Tue, 2024-07-02 at 11:57 +0200, Waka Ranai wrote:
> > command: "C:/Program Files/PostgreSQL/15/bin/pg_resetwal" -f -x 3466214 "C:/Program Files/PostgreSQL/15/data" >>
"C:/ProgramFiles/PostgreSQL/15/data/pg_upgrade_output.d/20> 
> > pg_resetwal: error: could not delete file "pg_wal/000000010000000000000001": No such file or directory
>
> Hi again, I eventually found out that Cortex XDR was also installed on the system,
> but even after uninstalling it, I'm still faced with the same issue. I try to monitor
> the resources that might have a handle on the file, but the only ones shown are from
> postgres (one from postgres.exe and one from pg_resetwal). I did the monitoring with
> the bundled Resource Monitor of Microsoft, do you have any recommendations for another
> monitoring tool with automatic scanning maybe ?

I am not a Windows person; sorry.

> How could I make sure that the issue is not due to an internal postgres process ?

No idea - but the problem only happens for you, and as you say, it happens
always.  Why would PostgreSQL do something else on your system only?

> Did you consider not failing the upgrade if the file cannot be deleted ? What would
> be the problems, if any, in that use case ?

Should PostgreSQL be resilient to important files being removed from under it?
I think not...

Yours,
Laurenz Albe