| From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL 19 Beta 1 release announcement draft |
| Date: | 2026-06-02 07:55:45 |
| Message-ID: | 0430257a-03ea-4767-9ecc-75c4fa624ce0@app.fastmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 1, 2026, at 23:33, Joel Jacobson wrote:
> On Fri, May 29, 2026, at 05:23, Jonathan S. Katz wrote:
>> Hi,
>>
>> Attached is the draft of the PostgreSQL 19 Beta 1 release announcement.
>> Please review for accuracy (e.g. are features described correctly? Did I
>> miss a revert), recommendations on additions or glaring omissions,
>> structure, etc.
>>
>> Please provide feedback no later than June 4, 2026 12:00 UTC (though
>> preferably earlier!)
>
> Shameless plug: maybe the LISTEN/NOTIFY optimization could be added?
>
> The work to fix the problem was triggered when I saw the
>
> "Postgres LISTEN/NOTIFY does not scale"
>
> article posted on Hacker News front-page [1] [2].
As a possible, admittedly imperfect, signal of newsworthiness, searching
Hacker News for "Postgres" over the past year currently shows the article
as the #3 most popular story [4]. Hacker News is not the PostgreSQL user
base, of course, but it seems reasonable to assume there is some overlap.
> If of interest, maybe plug in this sentence
>
> "better LISTEN/NOTIFY scalability for multi-channel workloads"
>
> at the end of the ### Performance paragraph that begins with:
> "PostgreSQL 19 shows up"?
>
> /Joel
>
> [1] https://news.ycombinator.com/item?id=44490510
> [2] https://www.recall.ai/blog/postgres-listen-notify-does-not-scale
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2026-06-02 07:57:55 | Re: Report oldest xmin source when autovacuum cannot remove tuples |
| Previous Message | Peter Smith | 2026-06-02 07:41:33 | Re: Proposal: Conflict log history table for Logical Replication |