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?



This email and any files transmitted with it are intended solely for the use of 
the individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager. This message contains 
information that is intended only for the individual named. If you are not the 
named addressee you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately by e-mail if you have received this e-mail 
by mistake and delete this e-mail from your system. If you are not the intended 
recipient you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly prohibited.

-----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


On 2017-08-09 22:03:43 +0000, 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 00000000000000DF0000004C, offset 12148736
> I believe this means the standby server received WAL file out of order?  But 
> why did it crash?  Is crashing normal behavior in case like this?

This likely just means that that's the end of the WAL.

- Andres

Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:

Reply via email to