Re: pgsql: Avoid improbable PANIC during heap_update.

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Avoid improbable PANIC during heap_update.
Date: 2022-10-06 16:28:36
Message-ID: 20221006162836.hsbtfjyi23hbtnrn@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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)

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-10-06 17:35:38 pgsql: Remove MemoryContextContains().
Previous Message Tom Lane 2022-10-06 16:27:44 pgsql: Take care to de-duplicate entries in standby.c's table of locks.

Browse pgsql-hackers by date

  From Date Subject
Next Message Zheng Li 2022-10-06 16:40:10 Re: Support logical replication of DDLs
Previous Message Fujii Masao 2022-10-06 16:26:09 Re: list of acknowledgments for PG15