Re: PostgreSQL 19 GA press release draft

On 11/2/26 1:46 AM, Joel Jacobson wrote:
> On Mon, Nov 2, 2026, at 04:54, Jonathan S. Katz wrote:
>> Attached is the first draft of the PostgreSQL 19 press release.
>
> Thanks for working on this!
>
>> * Glaring omissions and/or items that should be removed
> ...
>> The press release content will be finalized on Nov 8, 2026. This is to
>> ensure we give our press release translators enough time to finish their
>> work ahead of the release. Please ensure you've provided all of your
>> feedback before that.
>
> Could we include the LISTEN/NOTIFY improvement,
> as we did in the Beta 1 announcement [1]?
>
> The Recall.ai article
>
> "Postgres LISTEN/NOTIFY does not scale" [2]
>
> reached #1 on the Hacker News front page and attracted substantial
> discussion [3]. I have verified with Recall.ai that the improvement
> addresses their specific use case. They have also updated the article
> to credit the PostgreSQL community for resolving the bottleneck.
>
> I think this makes the improvement newsworthy: readers who learned
> about the problem through that coverage would benefit from knowing
> that PostgreSQL 19 addresses the use case that prompted it.
>
> The sentence we agreed on for Beta 1 seems appropriate:
>
> There are also improvements for LISTEN/NOTIFY scalability
> that impact multi-channel workloads.
>
> I suggest adding it at the end of the performance paragraph in
>
> ### Developer experience and performance enhancements
Yup, I would classify this as a notable omission.

How is this for a sentence - I don't just want to lift from the beta
announcement, and I want to give more context around the usage:

==
There are also scalability improvements when using
[`LISTEN`](https://www.postgresql.org/docs/current/sql-listen.html) and
[`NOTIFY`](https://www.postgresql.org/docs/current/sql-notify.html) or
sending notifications that impact multi-channel workloads.
==