Re: documentation updates for SQL:2023
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-04-05T09:41:47Z
Lists: pgsql-hackers
On 01.03.23 10:12, Peter Eisentraut wrote: > SQL:2023 should be published within the next 2 months, so I want to > update our SQL conformance information for our PostgreSQL release later > this year. > > Attached are patches that update the keywords list and the features list > as usual. (Some of the new features in the JSON area are still being > worked on. I have just set them all to NO for now, to be revisited later.) I have committed these patches. > I'm also proposing to get rid of the tracking of subfeatures. This has > been de-facto deprecated: All the subfeatures for optional features have > been removed (replaced by top-level feature codes), and the subfeatures > for mandatory features aren't very interesting. The TODO is to remove > the columns for the subfeatures in src/backend/catalog/sql_features.txt. > That is a mechanical change that I did not include in the patch. I have dropped this for now. This got a little bit more complicated than I had hoped, since the sql_features.txt file is also loaded into the information schema in initdb, and I didn't want to reorganize that right now. Something to revisit some other time, perhaps.
Commits
-
doc: Update SQL features/conformance information to SQL:2023
- c9f57541d970 16.0 landed
-
doc: Update SQL keywords list to SQL:2023
- 1993f3feb74f 16.0 landed