| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com>, Stepan Neretin <slpmcf(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fix archive restore race that could unlink WAL before rename |
| Date: | 2026-08-05 22:16:43 |
| Message-ID: | anO2S2K1vQaw8zLj@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 05, 2026 at 04:07:02PM +0500, Andrey Borodin wrote:
>
>
> > On 5 Aug 2026, at 15:12, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> >
> > there is no point in including the test at all
>
> There's no point in committing the test. There is a point in writing
> test to demonstrate and describe bug with the test. That's why I
> recommend writing test in a separate patch.
As my previous words may be a bit confusing. Proving a bug in the
shape of a test is super useful, even if the so-said test finishes by
not being committed.
>> One thing that may be worth adding is a mention that we care about
>> concurrent WAL senders
>
> +1.
I'll do that, and likely apply the result. Another part is if this
should be backpatched or not, but I always find these recovery changes
quite stressing to do in stable branches, so for now I'd tend to just
do this change on HEAD, also due to the fact that we don't seem to
have reports about this tiny window being a problem in practice.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2026-08-05 22:17:16 | Re: [Patch]The Case For WAL-Logging pg_upgrade |
| Previous Message | Michael Paquier | 2026-08-05 22:12:20 | Re: [PATCH v1 0/3] Route crypto through the OpenSSL 3 provider API |