Re: BUG #16833: postgresql 13.1 process crash every hour

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Alex F <phoedos16(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16833: postgresql 13.1 process crash every hour
Date: 2021-05-14 22:10:01
Message-ID: CAH2-Wz=MQ2qVsGTqB-p6K=auyqiuwWawY8VrHkV1iaqwZMzB+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, May 14, 2021 at 1:13 PM Alex F <phoedos16(at)gmail(dot)com> wrote:
> Thanks for your support!

I just pushed a commit that adds hardening that will be sufficient to
prevent this being a hard crash. Of course the index should not become
corrupt in the first place, but at least in Postgres 13.4 the same
scenario will result in an error rather than in a hard crash.

Thanks
--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2021-05-15 00:20:47 Re: Segmentation fault when calling BlessTupleDesc in a C function in parallel on PostgreSQL-(12.6, 12.7, 13.2, 13.3)
Previous Message Tom Lane 2021-05-14 21:18:40 Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties