| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kolla, Mahesh" <Mahesh(dot)Kolla(at)transunion(dot)com> |
| Cc: | Eric Radman <ericshane(at)eradman(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15078: Unable to receive data from WAL Stream Error |
| Date: | 2018-02-22 18:19:27 |
| Message-ID: | 22119.1519323567@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Kolla, Mahesh" <Mahesh(dot)Kolla(at)transunion(dot)com> writes:
> Thank you for the response. Primary is accepting the ssl connections .Stand by is in sync with primary all the time but we receive FATALS sometimes 3 to 4 times a day which make us worry if having any data corruption
I doubt this is a PG bug; it sounds more like a networking problem.
Maybe there's a router or firewall in between that is timing out your
connections too easily. If you can't adjust the network infrastructure,
you could try enabling TCP keepalives (with a shorter repeat
interval than the default) on the replication connections.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kolla, Mahesh | 2018-02-22 18:43:38 | RE: BUG #15078: Unable to receive data from WAL Stream Error |
| Previous Message | Kolla, Mahesh | 2018-02-22 17:36:45 | RE: BUG #15078: Unable to receive data from WAL Stream Error |