On Thu, Sep 4, 2025 at 7:14 AM Arseniy Mukhin <[email protected]> wrote:
> Interesting, have you shared your patch and results somewhere? IIUC > Tom's approach resolves this bug, because with it we have queue > entries produced by committed transactions only, so we don't need to > check their status and don't have dependency on clog. I was eventually able to get better numbers with the patch after using a substantial number of connections, so I have now posted it here. [1]. > Another question: how to truncate notification data queue. It sounds > like it will be more difficult to figure out what data in the queue is > still needed. Yeah, I will think about this some more, and follow up with another patch. Thanks, Rishu [1] https://www.postgresql.org/message-id/CAK80%3DjipUfGC%2BU QSzeA4oCP9daRtHZGm2SQZWLxC9NWmVTDtRQ%40mail.gmail.com
