From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
Cc: | Rui DeSousa <rui(at)crazybean(dot)net>, Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Investigate postgres 9.6.3 repmgr lag 4.0.4 |
Date: | 2018-06-27 15:41:02 |
Message-ID: | 87po0cjkz5.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> writes:
> Hi all,
> it happened again. The weird thing is that when I query
> pg_stat_replication I see only one slave(the one that is still
> synced) and I dont see the second one. Moreover, I dont see anything
> in the repmgr log of the primary and in the slave regarding the
> disconnection...
Disclaimer: I am not a repmgr admin...
I suggest you check the DB server logs on both standby node and master
for evidence of connection attempts for streaming, their success/failure
and reasons and/or what might cause an established connection to drop.
That you don't see the rogue standby in pg_stat_replication on the
master is clear evidence that it's not connected presently but this
doesn't tell the whole story.
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800
From | Date | Subject | |
---|---|---|---|
Next Message | John Scalia | 2018-06-27 19:53:20 | Re: Upgrading 9.6.9 to 10.4 |
Previous Message | Rui DeSousa | 2018-06-27 15:34:14 | Re: Investigate postgres 9.6.3 repmgr lag 4.0.4 |