| From: | magodo <wztdyl(at)sina(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | how to know current xlog location on standby after primary is down |
| Date: | 2018-09-09 14:29:08 |
| Message-ID: | 4ffcd9e665cde2a7aaaaf55a3bc85145345e485c.camel@sina.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello,
I'm working on a high availability project for PG(v9.6).
Suppose I have a priamry-standby setup, I need to do promote once
primary is down, but only when standby is as new as primary (before it
is down). Therefore, I need a way to know the wal replay location on
standby.
I tried to set a hot standby, but it failed to run
`pg_current_xlog_location()` on it; I also tried `pg_xlogdump` on
standby, but it has following cavets:
- hard to identify latest used wal segment, since there are some
renamed reservations
- sometimes `pg_xlogdump` will raise errors like: "pg_xlogdump:
FATAL: error in WAL record at 0/9F88F0F8: record with incorrect prev-
link 2020/20202020 at 0/9F88F130"
So I want to know what is the correct way to do it. Thank you in
advance!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kim Rose Carlsen | 2018-09-09 20:00:04 | Conflict between recovery thread and client queries on a hot standby replica |
| Previous Message | Ron | 2018-09-08 20:26:49 | Volume partitioning (was Re: pgbackrest when data/base is symlinked to another volume) |