Re: [PG19] Promotion hangs behind a backend blocked on a stuck client

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Manu <manuelreyesbravo(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>
Subject: Re: [PG19] Promotion hangs behind a backend blocked on a stuck client
Date: 2026-10-16 03:27:01
Message-ID: CAGRkXqReaEK9AeqrwwemZ1Lk04j3c2QqtPVUZV0zn-K-GTKGmA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Hayato, you are right, thanks. v4-0001 sets the latch again if a
barrier is still pending, as Manu suggested. With your change on top,
DROP DATABASE waited 60 seconds with v2-0001 and 15 ms with v4-0001.

Manu, I took all of your test changes. On 19 and master the test fails
without 0001 and passes with it.

I call these v4 so they don't get mixed up with Fujii's v3.

Thanks,
Shihao

Attachment Content-Type Size
v4-0002-Test-barrier-absorption-with-a-stuck-client.patch application/x-patch 4.4 KB
v4-0001-Absorb-ProcSignalBarriers-while-waiting-for-the-c.patch application/x-patch 2.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-10-16 03:37:19 Re: [PG19] pg_upgrade from <= 18 loses the newest multixid if its members end at offset wraparound
Previous Message shveta malik 2026-10-16 03:26:34 Re: Proposal: Conflict log history table for Logical Replication