Re: Requested WAL segment xxx has already been removed

2025-07-15 Thread Alexander Kukushkin
On Tue, 15 Jul 2025 at 12:08, Japin Li wrote: > > IIRC, the standby will indefinitely attempt to connect for replication, > even > without restore_command configured. > That's correct. However right now it just results in an attempt to open the WAL segment in pg_wal and failing, what is cheap. C

Re: Requested WAL segment xxx has already been removed

2025-07-15 Thread Japin Li
On Tue, 15 Jul 2025 at 11:24, Alexander Kukushkin wrote: > Hi, > > On Mon, 14 Jul 2025 at 11:24, Japin Li wrote: > > The configuration is as expected. My test script simulates two distinct hosts > by utilizing local archive storage. > > For physical replication across distinct hosts without sh

Re: Requested WAL segment xxx has already been removed

2025-07-15 Thread wenhui qiu
HI >What is really painful right now, logical walsenders can only look into pg_wal, and unfortunately replication slots don't give 100% guarantee for WAL >retention because of max_slot_wal_keep_size. >That is, using restore_command for logical walsenders would be really helpful and solve some probl

Re: Requested WAL segment xxx has already been removed

2025-07-15 Thread Alexander Kukushkin
Hi, On Mon, 14 Jul 2025 at 11:24, Japin Li wrote: > The configuration is as expected. My test script simulates two distinct > hosts > by utilizing local archive storage. > > For physical replication across distinct hosts without shared WAL archive > storage, WALs are archived locally (in my test

Re: Requested WAL segment xxx has already been removed

2025-07-15 Thread wenhui qiu
HI Japin Thank you for your working on this.It is useful ,when a standby node has hardware issue repaired ,wal log usually has been archived.The wal_keep_size parameter is difficult to estimate accurately, as hardware repair or replacement times are often unpredictable. If the machine can be fix

Re: Requested WAL segment xxx has already been removed

2025-07-14 Thread Japin Li
On Mon, 14 Jul 2025 at 20:33, Fujii Masao wrote: > On 2025/07/14 17:08, Japin Li wrote: >> 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

Re: Requested WAL segment xxx has already been removed

2025-07-14 Thread Fujii Masao
On 2025/07/14 17:08, Japin Li wrote: 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 00010

Re: Requested WAL segment xxx has already been removed

2025-07-14 Thread Japin Li
On Mon, 14 Jul 2025 at 10:21, Alexander Kukushkin wrote: > On Mon, 14 Jul 2025 at 10:08, Japin Li wrote: > > 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_REPLIC

Re: Requested WAL segment xxx has already been removed

2025-07-14 Thread Alexander Kukushkin
On Mon, 14 Jul 2025 at 10:08, Japin Li wrote: > > 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