Horton
Menu

Re: Add progressive backoff to XactLockTableWait functions

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Xuneng Zhou <xunengzhou@gmail.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Andres Freund <andres@anarazel.de>, Kevin K Biju <kevinkbiju@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-08-07T18:20:33Z
Lists: pgsql-hackers 
Xuneng Zhou <xunengzhou@gmail.com> writes:
> V9 replaces the original partitioned xid-wait htab with a single,
> unified one, reflecting the modest entry count and rare contention for
> waiting. To prevent possible races when multiple backends wait on the
> same XID for the first time in XidWaitOnStandby, a dedicated lock has
> been added to protect the hash table.

This seems like adding quite a lot of extremely subtle code in
order to solve a very small problem.  I thought the v1 patch
was about the right amount of complexity.

			regards, tom lane

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Allow logical decoding on standbys