Re: Critical failure of standby

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: James Sewell <james(dot)sewell(at)jirotech(dot)com>
Cc: Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Critical failure of standby
Date: 2016-08-16 07:55:00
Message-ID: CANP8+jK+jXcoAV-d2_Y7iAP4nXSvb93HkQV8GDUfrxCR6cg+5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 16 August 2016 at 08:11, James Sewell <james(dot)sewell(at)jirotech(dot)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/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Amitabh Kant 2016-08-16 08:27:12 Re: Uber migrated from Postgres to MySQL
Previous Message Gavin Flower 2016-08-16 07:52:33 Re: C++ port of Postgres