Re: [PATCH] Harden recovery/t/051_effective_wal_level against WAL recycling

From: Bryan Green <dbryan(dot)green(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Harden recovery/t/051_effective_wal_level against WAL recycling
Date: 2026-08-13 13:42:55
Message-ID: 1d2c7102-3860-48a4-b2ad-5d5461abead8@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/12/26 06:26, Álvaro Herrera wrote:
> Hello Bryan,
>
> On 2026-Aug-10, Bryan Green wrote:
>
>> On 8/8/26 22:44, Bryan Green wrote:
>>
>>> In recovery/t/051_effective_wal_level.pl, standby3, standby4, and standby5
>>> are all init_from_backup()'d from 'my_backup', taken near the top of the
>>> test, and started much later, after the primary has produced and recycled a
>>> lot of WAL.  Nothing keeps the WAL they need to reach consistency: no slot
>>> covering it, no wal_keep_size, no archive.
>>
>> I have a use case that is not stock PG that this is related to. I'm
>> withdrawing this.
>
> You have a use case for ... this test remaining borderline broken? I'm
> wondering if you wanted to reply to some other thread.
>
> Thanks
>
Ah, you are correct. This was meant for another thread. Not withdrawn.

Thanks

--
Bryan Green
https://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2026-08-13 13:50:34 Re: Logical replication row filter loses unchanged toasted columns
Previous Message Palak Chaturvedi 2026-08-13 13:30:04 Re: Better shared data structure management and resizable shared data structures