| From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Arseniy Mukhin" <arseniy(dot)mukhin(dot)dev(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Fix LISTEN startup race with direct advancement |
| Date: | 2026-05-27 10:43:54 |
| Message-ID: | e0f950e2-8394-466c-bec9-4557c47bfd05@app.fastmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 26, 2026, at 17:40, Tom Lane wrote:
> 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.)
How about renaming listening to removeOnAbort and negating its meaning?
> 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.
I agree. I should have said that feel free to remove them.
(Would be nice with a way to attach tests that are meant to be thrown away,
but still let cfbot include them in testing.)
/Joel
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Fix-NOTIFY-wakeups-for-pre-commit-LISTEN-entries.patch | application/octet-stream | 6.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-05-27 10:47:32 | Re: PostgreSQL and OpenSSL 4.0.0 |
| Previous Message | shveta malik | 2026-05-27 10:38:40 | Re: Proposal: Conflict log history table for Logical Replication |