Re: Postgres Replication stopped

That second one is because your "max_wal_size" is too small. Increase it so
your checkpoints do not happen more often than your your
"checkpoint_timeout" setting.

- Lev

On Mon, Jun 10, 2019, 12:20 AM Mahmoud Moharam, <mmoharam(at)lucidya(dot)com>
wrote:

> Thanks for your kind reply
> I found this log too
>
> LOG: checkpoints are occurring too frequently (28 seconds apart)
> HINT: Consider increasing the configuration parameter "max_wal_size"
>
>
> On Mon, Jun 10, 2019 at 8:31 AM Alvaro Aguayo Garcia-Rada <
> aaguayo(at)opensysperu(dot)com> wrote:
>
>> That seems like a connection issue. Is the connection ovr a LAN? Or a
>> VPN? There might have been some interruption, from a damaged cable to an
>> isp problem
>>
>> Regards,
>>
>> Alvaro Aguayo
>> Operations Manager
>> Open Comb Systems E.I.R.L.
>>
>> (+51-1) 337-7813 Ext. 4002
>> www.ocs.pe
>>
>> ----- Original Message -----
>> From: "Mahmoud Moharam" <mmoharam(at)lucidya(dot)com>
>> To: "pgsql-admin" <pgsql-admin(at)lists(dot)postgresql(dot)org>, "pgsql-admin" <
>> pgsql-admin(at)postgresql(dot)org>
>> Sent: Monday, 10 June, 2019 01:24:26
>> Subject: Postgres Replication stopped
>>
>> Hi All ,
>>
>> I faced some issues on postgres replication as it was stopped with these
>> errors :-
>>
>> LOG: unexpected EOF on client connection with an open transaction
>> LOG: could not send data to client: Broken pipe
>> FATAL: connection to client lost
>> on DB Master
>>
>> thanks in advance
>>
>