| From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL 19 GA press release draft |
| Date: | 2026-11-02 19:37:57 |
| Message-ID: | f165b5b7-dc8a-4385-9294-3d004872f755@app.fastmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 2, 2026, at 14:05, Jonathan S. Katz wrote:
> 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.
> ==
How about:
==
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) to
exchange notifications in multi-channel workloads.
==
/Joel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2026-11-02 19:44:45 | Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation |
| Previous Message | Ilia Evdokimov | 2026-11-02 19:13:19 | Assertion failure when importing expression statistics with nested JSON values |