Re: how to know current xlog location on standby after primary is down

On Sun, Sep 09, 2018 at 10:29:08PM +0800, magodo wrote: > So I want to know what is the correct way to do it. Thank you in > advance! There are pg_last_wal_receive_lsn() and pg_last_wal_replay_lsn() which allow you to know what is the last LSN received and replayed on a standby. Those can be used

RE: connection error

Hi, Are you sure it is /23 and not /32 for the CIDR notation ? hostall all 127.0.0.1/32 trust hostall all 127.0.0.1/23 trust hostall all 172.29.1

Conflict between recovery thread and client queries on a hot standby replica

Hi It seems that the recovery thread(streaming replication) and sql queries against a postgresql hot standby can produce a deadlock. If you have conflicting statements running on master and slave, you can end up with queries on the slave waiting for locks of the recovery thread and the recov

Conflict between recovery thread and client queries on a hot standby replica

Hi It seems that the recovery thread(streaming replication) and sql queries against a postgresql hot standby can produce a deadlock. If you have conflicting statements running on master and slave, you can end up with queries on the slave waiting for locks of the recovery thread and the recov

how to know current xlog location on standby after primary is down

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