Re: [ADMIN] Unable to start postgres instance.
| От | Andrew Foster |
|---|---|
| Тема | Re: [ADMIN] Unable to start postgres instance. |
| Дата | |
| Msg-id | 97DA662B-D41B-4C0A-AAAD-DC1702C7A7EE@educationalmeasures.com обсуждение исходный текст |
| Ответ на | Re: [ADMIN] Unable to start postgres instance. ("Gone, Sajan" <SGone@lb.com>) |
| Ответы |
Re: [ADMIN] Unable to start postgres instance.
(Cachique <cachique@gmail.com>)
|
| Список | pgsql-admin |
Afternoon Sajan,
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.
--
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.
I would try setting your wal_keep_segments to a higher value on the master server. Depending on available HDD space on the master, you should be able to keep a few dozen without any issues. Also, here is a link to a resource that helped me with replication and seems to be a bit better than the one you included upthread. https://wiki.postgresql.org/wiki/Streaming_Replication
Best,
Andrew Foster | Educational Measures, LLC
Database Administrator
7100 E. Belleview Ave, Suite 350
Database Administrator
7100 E. Belleview Ave, Suite 350
On Apr 27, 2017, at 3:43 PM, Gone, Sajan <SGone@lb.com> wrote:
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@openscg.com>
Date: Thursday, April 27, 2017 at 3:45 PM
To: Sajan Gone <sgone@lb.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: [ADMIN] Unable to start postgres instance.
Date: Thursday, April 27, 2017 at 3:45 PM
To: Sajan Gone <sgone@lb.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: [ADMIN] Unable to start postgres instance.
On Thu, Apr 27, 2017 at 3:38 PM, Gone, Sajan <SGone@lb.com> wrote:
-bash-4.3$ psql -U postgrespsql: FATAL: the database system is starting upHowever its been on that from quite a long time. It would really appreciate if anyone could explain me on what is really going on.
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",
"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.
В списке pgsql-admin по дате отправления: