| From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Wal fetching standby refuses to promote |
| Date: | 2018-03-15 17:55:09 |
| Message-ID: | 87a7v9rzpe.fsf@jsievers.enova.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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 | Dino Mifsud | 2018-03-16 08:56:11 | restore OIDs |
| Previous Message | Grigory Smolkin | 2018-03-15 14:22:12 | Re: Backup Tool |