From: Noah Misch <noah@leadboat.com>
To: Alexander Lakhin <exclusion@gmail.com>
To: Nitin Motiani <nitinmotiani@google.com>
To: Andres Freund <andres@anarazel.de>
To: pgsql-hackers@postgresql.org
Subject: Re: Inval reliability, especially for inplace updates
Date: Fri, 8 Nov 2024 17:02:36 -0800
Message-ID: <20241109010236.93.nmisch@google.com> (raw)
In-Reply-To: <20241103182925.93.nmisch@google.com>
References: <CAH5HC94r2ZKy_MhNaPUjn7NHkOFgbyBAgV2jaYSRt35BNWuOAA@mail.gmail.com>
<CAH5HC95rn4gON8zNrFXFY-Cn4z0NZuDU_1TDwKnafX_25_C0UA@mail.gmail.com>
<20241024025357.a8.nmisch@google.com>
<CAH5HC97fbvr63wJO23k6N0YmQh8BK3QE8ch3cQC=dWJJBxaCjw@mail.gmail.com>
<20241031013924.cd.nmisch@google.com>
<10ec0bc3-5933-1189-6bb8-5dec4114558e@gmail.com>
<20241031200139.b4@rfd.leadboat.com>
<20241101042052.4c.nmisch@google.com>
<20241101233829.9f.nmisch@google.com>
<20241103182925.93.nmisch@google.com>
On Sun, Nov 03, 2024 at 10:29:25AM -0800, Noah Misch wrote:
> Pushed as 0bada39.
>
> Buildfarm member hornet REL_15_STABLE was in the same hang. Other buildfarm
> runs 2024-10-25T13:51:02Z - 2024-11-02T16:04:56Z may hang the same way. It's
> early to make a comprehensive list of hung buildfarm members, since many
> reported infrequently even before this period. I'll wait a week or two and
> then contact the likely-hung member owners. I regret the damage.
Buildfarm members plover and (less likely) sevengill might be hung in this
way. Owners (bcc'd): if convenient, please check whether a buildfarm run that
started before 2024-11-02T16:04:56Z is still ongoing. If it is, please use
"kill -QUIT" on one of the long-running autovacuum workers.
If it's the same hang, one autovacuum worker will have stack frames like:
#37 0x0000555e8a4fabcb in CacheInvalidateHeapTupleCommon (prepare_callback=0x555e8a4fa320 <PrepareInplaceInvalidationState>, newtuple=newtuple@entry=0x0,
tuple=tuple@entry=0x7f168e9a74e8, relation=relation@entry=0x7f168f1738c8) at inval.c:1504
#38 0x0000555e8a094f7c in heap_inplace_update_and_unlock (relation=0x7f168f1738c8, oldtup=0x555eb277ea58, tuple=0x7f168e9a74e8, buffer=3) at heapam.c:6354
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-hackers@postgresql.org
Cc: noah@leadboat.com, exclusion@gmail.com, nitinmotiani@google.com, andres@anarazel.de
Subject: Re: Inval reliability, especially for inplace updates
In-Reply-To: <20241109010236.93.nmisch@google.com>
* 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