Re: [PATCH] Fix LISTEN startup race with direct advancement - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] Fix LISTEN startup race with direct advancement
Date
Msg-id 14717.1779810009@sss.pgh.pa.us
Whole thread
In response to Re: [PATCH] Fix LISTEN startup race with direct advancement  ("Joel Jacobson" <joel@compiler.org>)
List 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



pgsql-hackers by date:

Previous
From: "Euler Taveira"
Date:
Subject: Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
Next
From: Thom Brown
Date:
Subject: Re: First draft of PG 19 release notes