From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Waka Ranai <wakadotranai@gmail.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: Bug report - pg_upgrade tool seems to have a race condition when trying to delete a pg_wal file
Date: Wed, 03 Jul 2024 10:44:30 +0200
Message-ID: <cb6770d34ab64200fa6628e23923a7d16a8c768f.camel@cybertec.at> (raw)
In-Reply-To: <CAP8Vo=9ib4wxrYt3NdwwL8t8bPG4=LafoiZCSa+chZRzB=30TA@mail.gmail.com>
References: <CAP8Vo=9o0FE6gzqZJ3XdeGPNqi=eNV3cM_6v-thE640YcYoWog@mail.gmail.com>
<3d6013e49ac684cf4e9fbb6a1eb28b068cc9c113.camel@cybertec.at>
<CAP8Vo=9Rp6MnE3LsNo5aAkjLNueXEXjDmjvBPF3AQEwbpnfXcA@mail.gmail.com>
<c3ea74ed3e44eaa31f8916a3e4a07c4a1eefa4df.camel@cybertec.at>
<CAP8Vo=_4xK06+vLefRv8wHy9FiEbn7uOFnu2wJQrvGNF7mT5OQ@mail.gmail.com>
<97f7b82147f7b84d0ce3e2a8e6cff3367faedc2e.camel@cybertec.at>
<CAP8Vo=9rYSNVDp+ohjTBFDk_H3JavdsUiLk+ptD7txR_uQAVeA@mail.gmail.com>
<CAP8Vo=9ib4wxrYt3NdwwL8t8bPG4=LafoiZCSa+chZRzB=30TA@mail.gmail.com>
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:/Program Files/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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: laurenz.albe@cybertec.at, wakadotranai@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Bug report - pg_upgrade tool seems to have a race condition when trying to delete a pg_wal file
In-Reply-To: <cb6770d34ab64200fa6628e23923a7d16a8c768f.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox