2020年8月8日(土) 15:37 Don Seiler <don@xxxxxxxxx>: > > PostgreSQL 9.6 > > I shut down the primary and promoted the replica (timeline advanced from 1 to 2). > > I then put a recovery.conf on the old primary so it would recover by WAL restore (not streaming). However it seems to refuse to see the new timeline. I do have recovery_target_timeline='latest', my full recovery.conf looks like this: > > standby_mode = 'on' > restore_command = 'envdir /etc/wal-g/environment /usr/local/bin/wal-g wal-fetch %f %p' > recovery_target_timeline = 'latest' > > However the new replica complains: > ERROR: 2020/08/08 06:28:34.876197 openpgp: invalid argument: no armored data found > ERROR: 2020/08/08 06:28:39.621300 Archive '000000010000142E0000005B' does not exist. > > The new primary wrote that file but under timeline 2, I see 000000020000142E0000005B in the archive, along with the expected 00000002.history file. After the failure to fetch the expected WAL file, the standby (replica) should be attempting to fetch the 00000002.history file; do you see any wal-g error messages about that? Regards Ian Barwick -- Ian Barwick https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
