From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL 17 release announcement draft |
Date: | 2024-09-07 18:05:00 |
Message-ID: | f6cbc634-81d4-4263-8434-86fa3537fc1e@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/6/24 6:40 PM, Jelte Fennema-Nio wrote:
> On Fri, 6 Sept 2024 at 19:04, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>> Please see v2 attached. As per original note, please provide feedback
>> before Mon, Sep 9 @ 12:00 UTC so we can begin the translation process.
>
> The following sentence was part of the beta1 release announcement, but
> is not part of this draft. Did that happen by accident or was it done
> on purpose? If on purpose, I'm curious why since I contributed the
> feature.
>
> "PostgreSQL 17 also provides better support for asynchronous and more
> secure query cancellation routines, which drivers can adopt using the
> libpq API."
The beta announcement typically calls out more of the features available
to ensure we can get folks testing them. Features that target API
integrations/internals aren't usually mentioned in the GA announcement.
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2024-09-07 18:11:43 | Re: Yet another way for pg_ctl stop to fail on Windows |
Previous Message | Tomas Vondra | 2024-09-07 15:27:05 | Re: Adding skip scan (including MDAM style range skip scan) to nbtree |