From: | Payal Singh <payals1(at)umbc(dot)edu> |
---|---|
To: | Bruyninckx Kristof <Kristof(dot)Bruyninckx(at)cegeka(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: replication terminated by primary server |
Date: | 2017-12-07 18:29:10 |
Message-ID: | CAK4ounxZNQ1_JHnsGttOPR8bA_MVEKJc+XuNtaW6Q85Wq+NNYQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Dec 6, 2017 at 8:07 AM, Bruyninckx Kristof <
Kristof(dot)Bruyninckx(at)cegeka(dot)com> wrote:
>
>
> In our environment, we have a master slave replication setup that has been
> working stable for the last year.
>
> Host systems are debian Jessie and we are using postgres 9.4.
>
> Now recently we have experienced a crash/hung master, and after restarting
> the postgress services on here the replication stopped working. The master
> however is running seemingly normal, except for the errors reported when it
> got restarted. After this nothing error related is reported.
>
Might want to check the master postgres logs during and after crash as
well. Also, check for wal file progress on master (select * from
pg_stat_archiver).
--
Payal Singh
Graduate Student
Department of Computer Science and Electrical Engineering
University of Maryland, Baltimore County
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2017-12-07 21:30:47 | Re: ERROR: too many dynamic shared memory segments |
Previous Message | Peter J. Holzer | 2017-12-07 14:01:52 | Re: Infinite replication loop with pglogical |