From: | Bimal <internetuser2008(at)yahoo(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org, Jerry Sievers <gsievers19(at)comcast(dot)net> |
Subject: | Re: Wal fetching standby refuses to promote |
Date: | 2018-03-18 16:26:42 |
Message-ID: | 1195397079.2731184.1521390402043@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
You can try to add the trigger file in recovery.conf and perform a promote. Never tried but should work. On Thursday, March 15, 2018, 10:56:06 AM PDT, Jerry Sievers <gsievers19(at)comcast(dot)net> wrote:
This was an atomic snapshot put in recovery and happily reading WALs
from the repo.
It's consistent and allows read-only querying. It's replayed a few days
worth of WALs and was previously running with a recovery_target_xid =
$some-xid which apparently was never hit and/or aborted.
It would not promote then, after pg_ctl promote. The 'promote' file did
get created in pgdata.
Now it's running again with recovery.conf that contains just...
standby_mode = on
restore_command = 'cp /somedir/%f %p'
Still it fails to respond to the issuance of a promote.
There is no trigger file config's in recovery.conf and we have never
needed to do same since pg_ctl promote usually works.
Any idea what's causing this?
Thanks
version
-----------------------------------------------------------------------------------------------------------------
PostgreSQL 9.6.6 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609, 64-bit
(1 row)
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800
From | Date | Subject | |
---|---|---|---|
Next Message | Tyler Collier | 2018-03-18 20:30:46 | Re: persist connection info from docker container |
Previous Message | Marco DE BOOIJ | 2018-03-18 12:22:31 | Re: Barman backup fails after upgrade to PostgreSQL 10 |