>-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
Hi,
Please quote properly on postgres mailing lists.
On 2017-08-09 22:31:23 +, Seong Son (US) wrote:
> I see. Thank you.
>
> But the Postgresql process had crashed at that time so the streaming
> replication was no longer working. Why would it crash and is that normal?
You've given 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 +,
Hi,
On 2017-08-09 22:03:43 +, Seong Son (US) wrote:
> 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
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
