Re: Optimize LISTEN/NOTIFY

From: "Joel Jacobson" <joel(at)compiler(dot)org>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Optimize LISTEN/NOTIFY
Date: 2025-10-27 06:18:37
Message-ID: 4b7b49a5-5e1a-44a8-93e0-60457d15cb1d@app.fastmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 27, 2025, at 02:27, Chao Li wrote:
>> On Oct 27, 2025, at 07:24, Joel Jacobson <joel(at)compiler(dot)org> wrote:
>>
>> Write-up of changes since v20:
>>
>> Two new fields have been added to QueueBackendStatus:
>> + QueuePosition advisoryPos; /* safe skip-ahead position */
>> + bool advancingPos; /* backend is reading the queue */
...
> I did a quick review on v21 only focusing on the “direct advancement” logic.
>
> In v21, you added advisoryPos and advancingPos which is same as my
> proposed solution. But you missed an important point from mine.
>
...
> From this perspective, we need to add a new field
> adviancingTillPos to QueueBackendStatus. (This field was also missing
> from my proposed patch).

I'm doubtful yet another field is worth the added complexity cost.

Before increasing the complexity further, I think we should first
try to simulate somewhat realistic workloads, to see if we actually
have a problem first.

/Joel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-10-27 06:41:11 Re: Logical Replication of sequences
Previous Message Quan Zongliang 2025-10-27 06:02:41 Re: [PATCH] Little refactoring of portalcmds.c