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

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Bryan Green <dbryan(dot)green(at)gmail(dot)com>
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-12 11:26:47
Message-ID: anoaxquC8RMNFfli@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"La vida es para el que se aventura"

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2026-08-12 11:44:02 Re: JSON_TABLE: table => column ON ERROR propagation
Previous Message Álvaro Herrera 2026-08-12 11:24:16 Re: LibreSSL and OpenSSL separation in libpq to support 1.1.1 deprecation