Updated to postgres13 on some nodes and seeing this error:
Feb 15 12:15:36 sd-prod-postgres202 pgreba[3338]: 2021/02/15 12:15:36 Error getting pg_current_wal_lsn: missing destination name written_lsn in *main.PgStatWalReceiver
Feb 15 12:15:37 sd-prod-postgres202 pgreba[6986]: 2021/02/15 12:15:37 Listening on :8000
Feb 15 12:15:37 sd-prod-postgres202 pgreba[6986]: 2021/02/15 12:15:37 Error getting pg_current_wal_lsn: missing destination name written_lsn in *main.PgStatWalReceiver
Feb 15 12:15:37 sd-prod-postgres202 pgreba[8504]: 2021/02/15 12:15:37 Listening on :8000
Feb 15 12:15:37 sd-prod-postgres202 pgreba[8504]: 2021/02/15 12:15:37 Error getting pg_current_wal_lsn: missing destination name written_lsn in *main.PgStatWalReceiver
Feb 15 12:15:37 sd-prod-postgres202 pgreba[10113]: 2021/02/15 12:15:37 Listening on :8000
Feb 15 12:15:37 sd-prod-postgres202 pgreba[10113]: 2021/02/15 12:15:37 Error getting pg_current_wal_lsn: missing destination name written_lsn in *main.PgStatWalReceiver
Feb 15 12:15:37 sd-prod-postgres202 pgreba[11487]: 2021/02/15 12:15:37 Listening on :8000
Feb 15 12:15:37 sd-prod-postgres202 pgreba[11487]: 2021/02/15 12:15:37 Error getting pg_current_wal_lsn: missing destination name written_lsn in *main.PgStatWalReceiver
This MR should fix this.
Tested that it doesn't break pg10:
$ pgvm cluster list
cluster in current environment (10.2):
my_cluster is online at port 5433
$ cat examples/local.yml | grep port
port: 5433
$ curl localhost:8000/replica
{"state":1,"postmaster_start_time":"2021-02-15 13:06:09.628 EST","role":"primary","xlog":{"location":22941688,"received_location":0,"replayed_location":null,"replayed_timestamp":null,"paused":false},"replication":[],"byte_lag":0}
Also tested that it doesn't break in pg10 replica:
Updated to postgres13 on some nodes and seeing this error:
This MR should fix this.
Tested that it doesn't break pg10:
Also tested that it doesn't break in pg10 replica: