Postgres Pro
Downloads
Home   >   mailing lists

Re: 2023-08-10 release announcement draft - Mailing list pgsql-hackers

From Donghang Lin
Subject Re: 2023-08-10 release announcement draft
Date
Msg-id CAA=D8a3b8-UnRm3OOrH_wiqHu-J-Tn9sG3rS_KTa+J71ZK-BdQ@mail.gmail.com
Whole thread Raw
In response to Re: 2023-08-10 release announcement draft  ("Jonathan S. Katz" <jkatz@postgresql.org>)
List pgsql-hackers
Tree view
Hi, 

Sorry, join late after the release note is out. 

>  * An out-of-memory error from JIT will now cause a PostgreSQL `FATAL` error instead of a C++ exception.

I assume this statement is related to this fix[1].
I think an OOM error from JIT causing a PostgreSQL `FATAL` error is the actual behavior before the fix.
What the fix does is to bring exceptions back to the c++ world when OOM happens outside of LLVM. 

Thanks,
Donghang Lin



On Wed, Aug 9, 2023 at 7:10 PM Jonathan S. Katz <jkatz@postgresql.org> wrote:
On 8/8/23 11:13 PM, Robert Treat wrote:

> "Users who have skipped one or more update releases may need to run
> additional, post-update steps; "
>
> The comma should be removed.
>
> "please see the release notes for earlier versions for details."
>
> Use of 'for' twice is grammatically incorrect; I am partial to "please
> see the release notes from earlier versions for details." but could
> also see "please see the release notes for earlier versions to get
> details."

Interestingly, I think this language has been unmodified for awhile.
Upon reading it, I agree, and took your suggestions.

Thanks,

Jonathan

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PoC] pg_upgrade: allow to upgrade publisher node
Next
From: Richard Guo
Date:
Subject: Simplify create_merge_append_path a bit for clarity