From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Joel Jacobson" <joel(at)compiler(dot)org> |
Cc: | "Arseniy Mukhin" <arseniy(dot)mukhin(dot)dev(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Optimize LISTEN/NOTIFY |
Date: | 2025-10-15 21:15:15 |
Message-ID: | 1319398.1760562915@sss.pgh.pa.us |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Joel Jacobson" <joel(at)compiler(dot)org> writes:
> I assume the separate "advisory" queue position field
> would actually need to be two struct fields, since a queue position
> consists of a page and an offset, right?
No, I'd think you'd have both
QueuePosition pos; /* backend has read queue up to here */
QueuePosition advisory_pos; /* backend could skip queue to here */
in QueueBackendStatus. The other seems way too confusing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2025-10-15 21:17:30 | Re: POC: enable logical decoding when wal_level = 'replica' without a server restart |
Previous Message | Joel Jacobson | 2025-10-15 21:10:47 | Re: Optimize LISTEN/NOTIFY |