Re: BUG #19032: In restore_command %f parameter does not support WAL partial files.

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: wszenajch(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19032: In restore_command %f parameter does not support WAL partial files.
Date: 2025-08-27 00:48:14
Message-ID: CAKFQuwYZ8kq3_ELyHe2vcaXkD2o_hbJXsAHFTgZdufqe4bK2NA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Aug 26, 2025 at 5:10 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 19032
> Logged by: Wojciech Szenajch
> Email address: wszenajch(at)gmail(dot)com
> PostgreSQL version: 17.6
> Operating system: Ubuntu 24.04.03 LTS
> Description:
>
> Using restore_command = 'cp /tmp/receivewal/%f %p' does not use WAL partial
> file during backup restore process.
>

While this seems un-documented in the user-facing documentation the source
code makes it clear this is intended behavior. If your
point-in-time-recovery flow requires the use of these files you will need
to manually manipulate them.

https://github.com/postgres/postgres/blob/85b380162cd6c66752d1dd020a2d9700da0903c9/src/backend/access/transam/xlog.c#L5347

(link to article about a custom archiving process relying on pg_receivewal)

It seems unfortunate that the pg_receivewal creates files with ".partial"
extensions that are semantically different from what the core system
".partial" files are. But if your archive process is custom (i.e., uses
something other than archive_command) it seems reasonable that any
restore_command you need to create would also be something custom. Going
by the documentation for only half of the process is going to lead to these
kinds of inconsistent results.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nantha kumar.T. 2025-08-27 02:39:22 Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
Previous Message Tom Lane 2025-08-26 15:16:46 Re: BUG #19031: pg_trgm infinite loop on certain cases