From: | Poul Kristensen <bcc5226(at)gmail(dot)com> |
---|---|
To: | "Hunley, Douglas" <douglas(dot)hunley(at)openscg(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: PostgresSQL 9.5 and systemd autorestart but without replication. |
Date: | 2016-10-13 15:45:20 |
Message-ID: | CAAOuvVp5pck9C6x7ycvBnbkx6nW_cZce1gOeWURuDT-4fdquPw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thank you for fast respons.
No. The recovery.conf has now replace a recovery.done file on the slave.
No errors in the pg_log. I have not earlier experienced this situation.
The feature of autorestart is really nice.
BTW: I do not quite understand why the recovery.conf are replaced with a
recovery.done file.
Thanks
/Poul
2016-10-13 16:30 GMT+02:00 Hunley, Douglas <douglas(dot)hunley(at)openscg(dot)com>:
>
> On Thu, Oct 13, 2016 at 6:00 AM, Poul Kristensen <bcc5226(at)gmail(dot)com>
> wrote:
>
>> This morning I noticed that my 2 PG virtual servers had made an automatic
>> restart at exactly the same time 00:00. The 2 servers is running and
>> accepting connections but no WALL sender and no WALL receicver is running.
>> Why don't replication follow up!
>> Do I have to make a new pg_basebackup from primarily to replica?
>> OS: RHEL 7.2
>>
>
> Is the recovery.conf file still present and valid in $PGDATA on the slave?
> Any errors in the slave's pg_log directory concerning the replication?
>
>
> --
> {
> "name" : "douglas j hunley",
> "email" : "douglas(dot)hunley(at)openscg(dot)com <doug(dot)hunley(at)gmail(dot)com>",
> "title" : "database engineer",
> "phone" : "+1 732 339 3419 x163"
> }
>
--
Med venlig hilsen / Best regards
Poul Kristensen
Linux-OS/Virtualizationexpert and Oracle DBA
From | Date | Subject | |
---|---|---|---|
Next Message | Keith | 2016-10-13 15:58:25 | Re: Distribution shipped vs Postgres Repository |
Previous Message | Matteo Fabbri | 2016-10-13 15:18:21 | Re: pg_restore --clean --create reference documentation incongruity |