On 8/22/26 11:12 PM, cca5507 wrote:
Logs of standby
===============
2026-08-22 22:59:08.663 CST [49194] LOG: started streaming WAL from primary at
0/03000000 on timeline 1
2026-08-22 22:59:08.674 CST [49194] LOG: replication terminated by primary
server
2026-08-22 22:59:08.674 CST [49194] DETAIL: End of WAL reached on timeline 1
at 0/03052948.
2026-08-22 22:59:08.677 CST [49193] LOG: new target timeline is 2
2026-08-22 22:59:08.677 CST [49193] LOG: invalid record length at 0/03052948:
expected at least 24, got 0
2026-08-22 22:59:08.678 CST [49194] FATAL: could not create replication slot
"pg_walreceiver_49195": ERROR: replication slot "pg_walreceiver_49195" already
exists
2026-08-22 22:59:08.682 CST [49196] LOG: started streaming WAL from primary at
0/03000000 on timeline 2
The bug has been reproduced.
Fix
===
Make sure that the walreceiver creates temp slot only once.
After testing, it was confirmed that it did not occur again. I'm
planning to conduct another long-term test.
Thoughts?
