Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s72gA-003GjZ-7K for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2024 00:39:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s72gA-005MlJ-2K for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2024 00:39:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s72g9-005MlB-PO for pgsql-hackers@lists.postgresql.org; Wed, 15 May 2024 00:39:33 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s72g7-000FNM-5W for pgsql-hackers@postgresql.org; Wed, 15 May 2024 00:39:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=2lDgmYb9qGdIA1PY+mxccOmnbCHzJBc39V7vsfXnWdk=; b=UK0tS pgKUrFzxvIIIzLbUknKD8Z+Jmear/0T1Cn8wOlVgYBmjZ0nDRHFAkUnIKDXzPL4iTzlv4VuVdiFgG /fDW2P1xr0D1hT39I523PISa9xlyspPMtInVngHAjD+0lRABmmR2lB8yQW1DUrxv1VL5a5R9ABzsn B/hn8VuHo9gGRPFXqlDXnP7BLJe1E6Cjy2Bs2LXa4UwELUKB5nwC1vaOABf/S7MZp0JhyNEIfEDiR A396N7xqcjnBfJAfTKROQkBjEJE3xl32HgmpeABTtRHg3eZZk5z/4kUrEWncoJs3exSZ7fJAepiY3 k0tvctvh51Kk8l5SA+sDnZ8W30kcw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1s72g5-008MBe-27; Tue, 14 May 2024 20:39:29 -0400 Date: Tue, 14 May 2024 20:39:29 -0400 From: Bruce Momjian To: Andrew Dunstan Cc: PostgreSQL-development Subject: Re: First draft of PG 17 release notes Message-ID: References: <58757e3e-4ac7-488f-8556-34aa6430c225@dunslane.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <58757e3e-4ac7-488f-8556-34aa6430c225@dunslane.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, May 11, 2024 at 03:32:55PM -0400, Andrew Dunstan wrote: > > On 2024-05-09 Th 00:03, Bruce Momjian wrote: > > I have committed the first draft of the PG 17 release notes; you can > > see the results here: > > > > https://momjian.us/pgsql_docs/release-17.html > > > > It will be improved until the final release. The item count is 188, > > which is similar to recent releases: > > > > release-10: 189 > > release-11: 170 > > release-12: 180 > > release-13: 178 > > release-14: 220 > > release-15: 184 > > release-16: 206 > > release-17: 188 > > > > I welcome feedback. For some reason it was an easier job than usual. > > > I don't like blowing my own horn but I feel commit 3311ea86ed "Introduce a > non-recursive JSON parser" should be in the release notes. This isn't > something that's purely internal, but it could be used by an extension or a > client program to parse JSON documents that are too large to handle with the > existing API. > > Maybe "Introduce an incremental JSON parser" would have been a better > headline. Well, this gets into a level of detail that is beyond the average reader. I think at that level people will need to read the git logs or review the code. Do we use it for anything yet? It could be put in the source code section but I try to only have user-visible stuff there. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.