Re: pg_waldump: WAL in pg_wal.old/ inside a tar archive is read as WAL

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Raja Sai pranav <rajasaipranav0(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, sulamul(at)gmail(dot)com, robertmhaas(at)gmail(dot)com
Subject: Re: pg_waldump: WAL in pg_wal.old/ inside a tar archive is read as WAL
Date: 2026-11-20 22:50:26
Message-ID: awDOsusJThCWUzYG@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 20, 2026 at 07:22:11AM -0800, Raja Sai pranav wrote:
> So pg_wal.old/000000010000000000000038 or
> pg_wal/somedir/000000010000000000000038 is also taken as WAL. If such a
> file comes first in the archive, the real pg_wal/ copy is then skipped as a
> duplicate.

You are not mentioning which tool you are using is creating this
folder layer and particularly the reason behind this choice. In-core
configuration relies on max_wal_size as one way to control the size of
pg_wal/. So you are breaking at least one rule here.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2026-11-20 22:53:15 Re: Table AM callback for logical decoding support (REPACK CONCURRENTLY)
Previous Message Zsolt Parragi 2026-11-20 22:47:23 Re: EXPLAIN ANALYZE CREATE TABLE AS EXECUTE runs non-SELECT prepared statements