|
Hi Douglas,
Appreciate your help.
'hot_standby = on' set up was already made but I restarted the server just in case, however I am still getting the same error.
But when I am attempting to reboot the database this is what I have noticed on the error logs
LOG: started streaming WAL from primary at 0/1B000000 on timeline 1
FATAL: could not receive data from WAL stream: ERROR: requested WAL segment 00000001000000000000001B has already been removed
LOG: received fast shutdown request
LOG: shutting down
LOG: database system is shut down
So, I am assuming the WAL files have already been deleted on the Master. Is there any setting on Master I can toggle in order to increase the expiry(retention policy) for the WAL files.
Thank You,
Sajan Gone
Database Administrator
L Brands
Mobile #: 517-990-5282
Office #: 614-577-7622
From: "Hunley, Douglas" <douglas.hunley@xxxxxxxxxxx>
Date: Thursday, April 27, 2017 at 3:45 PM To: Sajan Gone <sgone@xxxxxx> Cc: "pgsql-admin@xxxxxxxxxxxxxx" <pgsql-admin@xxxxxxxxxxxxxx> Subject: Re: [ADMIN] Unable to start postgres instance. On Thu, Apr 27, 2017 at 3:38 PM, Gone, Sajan
<SGone@xxxxxx> wrote:
It is doing exactly what it should. A standby is, by default, in permanent recovery mode. If you wish to be able to connect to it in this mode, you need to add 'hot_standby = on' to its postgresql.conf and restart the standby. {
"name" : "douglas j hunley", "title" : "database engineer", Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LB may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. |
