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

From: Manu <manuelreyesbravo(at)gmail(dot)com>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, 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>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PG19] Promotion hangs behind a backend blocked on a stuck client
Date: 2026-10-16 03:39:54
Message-ID: 179212199496.455546.18038100053239795886@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> DROP DATABASE waited 60 seconds with v2-0001 and 15 ms with v4-0001.

Thanks, and nicely done pulling it together -- 60 s to 15 ms is a good
result. The test changes read right to me too, and the regression is
pinned now: it fails without 0001 and passes with it on 19 and master.

It's been a pleasure to help on this one. I'll keep an eye on the thread
and jump in wherever it is useful, the backpatch included -- the test
will want renumbering there, since 060 is taken on every branch now.

Regards,
Manu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2026-10-16 03:50:57 Re: Parallel TID Range Scan returns wrong results on rescan
Previous 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