Re: Standby got fatal after the crash recovery

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com>
Cc: Thunder <thunder1(at)126(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Standby got fatal after the crash recovery
Date: 2020-03-18 02:31:53
Message-ID: 20200318023153.GF214947@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 18, 2020 at 11:19:22AM +0900, Ian Barwick wrote:
> On 2020/03/17 12:53, Thunder wrote:
> > Sorry.
> > We are using pg11, and cloned from tag REL_11_BETA2.
>
> In that case you should upgrade to the current version
> in the PostgreSQL 11 series (at the time of writing 11.7).

Definitely. The closest things I can see in this area are 9a1bd8 and
c34f80 which had symptoms similar to what you have mentioned here with
btree_xlog_delete(), but that's past history.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message movead.li@highgo.ca 2020-03-18 02:48:09 Re: A bug when use get_bit() function for a long bytea string
Previous Message Ian Barwick 2020-03-18 02:19:22 Re: Standby got fatal after the crash recovery