Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue
Heikki Linnakangas <hlinnaka@iki.fi>
From: Heikki Linnakangas <hlinnaka@iki.fi>
To: Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>
Cc: Álvaro Herrera <alvherre@kurilemu.de>, Joel Jacobson <joel@compiler.org>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-11-07T08:10:25Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Clear 'xid' in dummy async notify entries written to fill up pages
- 84f1bf4afa5e 14.21 landed
- 21a9014cf00a 15.16 landed
- 0e8eaa2181d4 16.12 landed
- d80d5f099502 17.8 landed
- 82fa6b78dba1 18.2 landed
- 0bdc777e8007 19 (unreleased) landed
-
Fix remaining race condition with CLOG truncation and LISTEN/NOTIFY
- c2e58c0711fe 14.21 landed
- 0c862646cf2a 15.16 landed
- 44e8c60be66c 16.12 landed
- c2682810ab7d 17.8 landed
- 7b069a1876e4 18.2 landed
- 797e9ea6e54b 19 (unreleased) landed
-
Fix bug where we truncated CLOG that was still needed by LISTEN/NOTIFY
- eba917d360e7 14.21 landed
- 1a469d7b5b7d 15.16 landed
- 053e1868b7ee 16.12 landed
- d02c03ddc5e3 17.8 landed
- 321ec54625fd 18.2 landed
- 8eeb4a0f7c06 19 (unreleased) landed
-
Escalate ERRORs during async notify processing to FATAL
- 7cb05dd2d198 14.21 landed
- b1da37de21d4 15.16 landed
- c1a5bde003b8 16.12 landed
- b821c92920f0 17.8 landed
- aab4a84bb070 18.2 landed
- 1b4699090eaf 19 (unreleased) landed
-
Limit the size of TID lists during parallel GIN build
- c98dffcb7c70 19 (unreleased) cited
Attachments
On 06/11/2025 17:13, Arseniy Mukhin wrote: > Let's say we have the queue: > > (tail ... pos1 ... bad_entry_pos ... head) > > bad_entry_pos - position of the entry where TransactionIdDidCommit fails. > > We have the listener L1 with pos = pos1. It means every new listener > should process the queue from pos1 (as it's max(listener's pos)) up to > the queue head and when they try to do it, they will fail on > 'bad_entry'. Gotcha. >> Another small change we could make is to check for listenChannels == NIL >> before calling TransactionIdDidCommit. > > There is a comment that describes why we need this initial reading in > Exec_ListenPreCommit: > > /* > * This is our first LISTEN, so establish our pointer. > * > * We set our pointer to the global tail pointer and then move it forward > * over already-committed notifications. This ensures we cannot miss any > * not-yet-committed notifications. We might get a few more but that > * doesn't hurt. > > It seems that with such a check we will skip not-yet-committed > notifications and always get to the HEAD. If we decide that it's ok, > maybe we can just set 'pos' of every new listener to the HEAD without > reading? Right, I didn't mean skipping asyncQueueReadAllNotifications() altogether. Just the TransactionIdDidCommit() calls in it, when listenChannels == NIL, see attached patch. The idea is that when 'listenChannels == NIL', we're not going send the notification to the frontend regardless of what TransactionIdDidCommit says. If we don't call TransactionIdDidCommit, we won't fail on bad entries. I'm not sure how much this matters. We really shouldn't have bad entries in the queue to begin with. And if we do, a broken entry could cause all kinds of trouble. For example, if the broken entry's (bogus) XID is higher than current XID, XidInMVCCSnapshot() will return true and we'll get stuck on that. - Heikki