From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: First draft of PG 17 release notes |
Date: | 2024-09-11 14:36:35 |
Message-ID: | ZuGq82aGy1RDsx0w@nathan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)jeltef(dot)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(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2024-09-11 14:50:25 | Re: Add on_error and log_verbosity options to file_fdw |
Previous Message | Bruce Momjian | 2024-09-11 14:16:04 | Re: Detailed release notes |