Re: [PATCH] Fix LISTEN startup race with direct advancement
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Joel Jacobson" <joel@compiler.org>
Cc: "Arseniy Mukhin" <arseniy.mukhin.dev@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2026-05-26T15:40:09Z
Lists: pgsql-hackers
"Joel Jacobson" <joel@compiler.org> writes: > Ohh, right, thanks for spotting. New version attached, 0001 and 0002 identical, > and 0003 now only contain the fix. I agree with this fix, but it seems to me that it changes the meaning of the ListenerEntry.listening flag in a rather fundamental way. I'm tempted to rename that flag to "committed" or something like that. (Both "listening" and "committed" appear in dozens of places in this file that are not references to this flag, so TBH I'd rather use a flag name that is not either of those words. But I can't think of a better name.) Also, while the proposed test cases are good for showing that there's a bug here, I'm disinclined to commit them. I do not think there is value in them proportionate to the cost of two new isolation-test instances. regards, tom lane