pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Alexander Lakhin <exclusion@gmail.com>
To: Noah Misch <noah@leadboat.com>
To: pgsql-hackers@postgresql.org
Subject: Re: heap_inplace_lock vs. autovacuum w/ LOCKTAG_TUPLE
Date: Sun, 27 Oct 2024 08:00:00 +0300
Message-ID: <ec25f651-58ca-9266-e485-c561907d18e6@gmail.com> (raw)
In-Reply-To: <20241027040928.9e.nmisch@google.com>
References: <20241026184936.ae.nmisch@google.com>
	<20241027040928.9e.nmisch@google.com>

Hello Noah,

27.10.2024 07:09, Noah Misch wrote:
> On Sat, Oct 26, 2024 at 11:49:36AM -0700, Noah Misch wrote:
>> intra-grant-inplace-db.spec got a novel failure today:
>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sarus&dt=2024-10-26%2014%3A08%3A58
>>
>> The isolationtester_waiting query is supposed to detect that step vac2 is
>> blocked.  vac2 didn't finish within the timeout, but isolationtester_waiting
>> never considered it blocked.
>> ... work on reproducing this.

FWIW, there was a similar failure in August: [1], and I also could not
reproduce that locally, yet wrote a preliminary analysis at [2] in the
Unsorted section, in the hope to see it again and continue investigation.

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=iguana&dt=2024-08-29%2013%3A57%3A57
[2] https://wiki.postgresql.org/wiki/Known_Buildfarm_Test_Failures

Best regards,
Alexander

view thread (4+ messages)  latest in thread

Message-ID: <ec25f651-58ca-9266-e485-c561907d18e6@gmail.com>
Permalink:  ../ec25f651-58ca-9266-e485-c561907d18e6@gmail.com/
Also on:    postgresql.org/message-id/ec25f651-58ca-9266-e485-c561907d18e6@gmail.com

copy link · copy postgr.es

reply

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: exclusion@gmail.com, noah@leadboat.com
  Subject: Re: heap_inplace_lock vs. autovacuum w/ LOCKTAG_TUPLE
  In-Reply-To: <ec25f651-58ca-9266-e485-c561907d18e6@gmail.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