Re: [GENERAL] streaming replication - crash on standby

2017-08-11 Thread Seong Son (US)
>-Original Message- >From: Andres Freund [mailto:and...@anarazel.de] >Sent: Wednesday, August 09, 2017 6:34 PM >To: Seong Son (US) <seong@datapath.com> >Cc: pgsql-general@postgresql.org >Subject: Re: [GENERAL] streaming replication - crash on standby > &g

Re: [GENERAL] streaming replication - crash on standby

2017-08-09 Thread Seong Son (US)
. -Original Message- From: Andres Freund [mailto:and...@anarazel.de] Sent: Wednesday, August 09, 2017 6:27 PM To: Seong Son (US) <seong@datapath.com> Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] streaming replication - crash on standby Hi, On 2017-08-09 22:03:43 +,

[GENERAL] streaming replication - crash on standby

2017-08-09 Thread Seong Son (US)
The last line from pg_xlogdump of the last WAL file on the crashed standby server shows the following. pg_xlogdump: FATAL: error in WAL record at DF/4CB95FD0: unexpected pageaddr DB/62B96000 in log segment 00DF004C, offset 12148736 I believe this means the standby server

[GENERAL] standby database crash

2017-07-31 Thread Seong Son (US)
I have a client who has streaming replication setup with the primary in one city and standby in another city both identical servers with Postgresql 9.6 on Windows Server 2012. They have some network issues, which is causing the connection from the primary to standby to drop sometimes. And