From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Jaime Casanova <jcasanov@systemguards.com.ec>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Avoid improbable PANIC during heap_update.
Date: Thu, 6 Oct 2022 18:28:36 +0200
Message-ID: <20221006162836.hsbtfjyi23hbtnrn@alvherre.pgsql> (raw)
In-Reply-To: <YzVPfCKNrmi0aLEh@ahch-to>
On 2022-Sep-29, Jaime Casanova wrote:
> This doesn't look as improbable because I saw it at least 3 times with
> v15beta4.
To further the case of the not-so-low-probability, we have customers
that are hitting this about once per day, with Postgres 14 ... so their
systems are crashing all the time :-( We've collected a bunch of
backtraces, and while I didn't analyze all of them, I hear that they all
look related to this fix.
Not good.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
Maybe there's lots of data loss but the records of data loss are also lost.
(Lincoln Yeoh)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: alvherre@alvh.no-ip.org, jcasanov@systemguards.com.ec, tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Avoid improbable PANIC during heap_update.
In-Reply-To: <20221006162836.hsbtfjyi23hbtnrn@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox