Requested WAL segment xxx has already been removed

Japin Li <japinli@hotmail.com>

From: Japin Li <japinli@hotmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-14T08:08:06Z
Lists: pgsql-hackers

Attachments

Hi all,

I recently hit an error with our streaming replication setup:

  2025-07-14 11:52:59.361 CST,"replicator","",728458,"10.9.9.74:35724",68747f1b.b1d8a,1,"START_REPLICATION",2025-07-14 11:52:59 CST,3/0,0,ERROR,58P01,"requested WAL segment 00000001000000000000000C has already been removed",,,,,,"START_REPLICATION 0/C000000 TIMELINE 1",,,"standby","walsender",,0

It appears the requested WAL segment 00000001000000000000000C had already been
archived, and I confirmed its presence in the archive directory. However, when
the standby tried to request this file, the primary only searched for it in
pg_wal and didn't check the archive directory. I had to manually copy the
segment into pg_wal to get streaming replication working again.

My question is: Can we make the primary automatically search the archive if
restore_command is set?

I found that Fujii Masao also requested this feature [1], but it seems there
wasn't a consensus.

I've attached a script to reproduce this issue.

[1] https://www.postgresql.org/message-id/AANLkTinN%3DxsPOoaXzVFSp1OkfMDAB1f_d-F91xjEZDV8%40mail.gmail.com

-- 
Regards,
Japin Li