RE: BUG #15078: Unable to receive data from WAL Stream Error - Mailing list pgsql-bugs

From Kolla, Mahesh
Subject RE: BUG #15078: Unable to receive data from WAL Stream Error
Date
Msg-id 78e189efca37446b98eaacf2399ff1c2@transunion.com
Whole thread Raw
In response to Re: BUG #15078: Unable to receive data from WAL Stream Error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hello Tom,

We got information from network team saying that  primary and standby are communicating through a switch ,there is no
firewallat all 

Please let me know why we are getting below associated LOGS saying invalid resource manager   with the FATAL message
Unableto receive data from WAL Stream Error as well. It looks like  a bug  

> sh: dev/null: No such file or directory
> sh: dev/null: No such file or directory < 2018-02-19 01:37:48.860 CST
> > LOG:  invalid resource manager ID 48 at
> 15/2D69E848

Thank you
Mahesh Kolla

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Thursday, February 22, 2018 12:19 PM
To: Kolla, Mahesh <Mahesh.Kolla@transunion.com>
Cc: Eric Radman <ericshane@eradman.com>; pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15078: Unable to receive data from WAL Stream Error

"Kolla, Mahesh" <Mahesh.Kolla@transunion.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
networkinfrastructure, you could try enabling TCP keepalives (with a shorter repeat interval than the default) on the
replicationconnections. 

            regards, tom lane

Attachment

pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: BUG #15076: postmaster crashes unexpectedly when using up arrowkey in psql command
Next
From: PG Bug reporting form
Date:
Subject: BUG #15079: [54000] ERROR: total size of jsonb array elements exceedsthe maximum of 268435455 bytes