Re: Critical failure of standby - Mailing list pgsql-general

From James Sewell
Subject Re: Critical failure of standby
Date
Msg-id CAANVwEt57g1B=-zqS_839xDg+xRv_7iPgB9J29u5dgqpUNG_Vw@mail.gmail.com
Whole thread Raw
In response to Re: Critical failure of standby  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-general
Hi,

No, this was a one off in a network split situation.

I'll check the startup when I get a chance - thanks for the help.

Cheers,

James Sewell,
Solutions Architect 

 

Suite 112, Jones Bay Wharf, 26-32 Pirrama Road, Pyrmont NSW 2009

On Tue, Aug 16, 2016 at 5:55 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
On 16 August 2016 at 08:11, James Sewell <james.sewell@jirotech.com> wrote:
 
As per the logs there was a crash of one standby, which seems to have corrupted that standby and the two cascading standby.
  • No backups
  • Full page writes enabled
  • Fsync enabled
WAL records are CRC checked, so it may just be a bug, not corruption that affects multiple servers.

At the moment we know the Startup process died, but we don't know why.

Do you repeatedly get this error?

Please set log_error_verbosity = VERBOSE and rerun

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.

pgsql-general by date:

Previous
From: Patrick B
Date:
Subject: Re: Permissions pg_dump / import
Next
From: Patrick B
Date:
Subject: PGPASSWORD - More than one in a bash script