From: | Donghang Lin <donghanglin(at)gmail(dot)com> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: 2023-08-10 release announcement draft |
Date: | 2023-08-11 02:07:02 |
Message-ID: | CAA=D8a3b8-UnRm3OOrH_wiqHu-J-Tn9sG3rS_KTa+J71ZK-BdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)postgresql(dot)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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Guo | 2023-08-11 02:31:34 | Simplify create_merge_append_path a bit for clarity |
Previous Message | Bruce Momjian | 2023-08-11 01:45:38 | Re: [PoC] pg_upgrade: allow to upgrade publisher node |