Re: First draft of PG 17 release notes - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: First draft of PG 17 release notes
Date
Msg-id ZuGq82aGy1RDsx0w@nathan
Whole thread Raw
In response to Re: First draft of PG 17 release notes  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Wed, Sep 11, 2024 at 10:12:58AM -0400, Bruce Momjian wrote:
> On Tue, Sep 10, 2024 at 09:52:42AM -0700, Masahiko Sawada wrote:
>> On Mon, Sep 9, 2024 at 11:29 PM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
>> > For 1, I think adding them to the release notes makes total sense,
>> > especially if the new APIs are documented not only in source code, but
>> > also on the website. Nathan his change is of this type, so I agree
>> > with him it should be in the release notes.
>> 
>> +1. I think that the increment JSON parser that is already mentioned
>> in the release note would fall in this type too; it's not a feature
>> aimed just for extension authors, but it's kind of source and internal
>> changes IMO. Since the DSM registry feature is described in the doc, I
>> think it would make sense to have it in the release notes and probably
>> has a link to the "Requesting Shared Memory After Startup" section.
> 
> This commit?
> 
>     commit 8b2bcf3f287
>     Author: Nathan Bossart <nathan@postgresql.org>
>     Date:   Fri Jan 19 14:24:36 2024 -0600
>     
>         Introduce the dynamic shared memory registry.
> 
> Yes, we have time to add it.

Yes, that's the one.

-- 
nathan



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Detailed release notes
Next
From: Fujii Masao
Date:
Subject: Re: Add on_error and log_verbosity options to file_fdw