pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Daniel Gustafsson <daniel@yesql.se>
To: koizumistr@minos.ocn.ne.jp, pgsql-docs <pgsql-docs@lists.postgresql.org>
Cc: Peter Eisentraut <peter@eisentraut.org>
Subject: Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
Date: Fri, 23 Feb 2024 10:06:54 +0100
Message-ID: <98185277-F389-4B32-B0EB-D1D2DF52A8D0@yesql.se> (raw)
In-Reply-To: <170866661469.645.14101429540172934386@wrigleys.postgresql.org>
References: <170866661469.645.14101429540172934386@wrigleys.postgresql.org>

> On 23 Feb 2024, at 06:36, PG Doc comments form <noreply@postgresql.org> wrote:

> The correct result would be as follows:
> 
> F302 	  	INTERSECT table operator 	 
> F302-02 	  	INTERSECT ALL table operator 	 
> F303 	  	INTERSECT DISTINCT table operator 	 
> F304 	  	EXCEPT ALL table operator

This was changed recently in c9f57541d970 which changed subfeatures to
top-level features to match the SQL:2023 standard, F303 was previously a
sub-feature named F302-01.  That being said, I agree that it makes sense to
place F303 below F302-02 as per the attached, unless Peter (on cc:) objects.

--
Daniel Gustafsson

Attachments:

  [application/octet-stream] f303.diff (661B, ../98185277-F389-4B32-B0EB-D1D2DF52A8D0@yesql.se/2-f303.diff)
  download | inline diff:
diff --git a/src/backend/catalog/sql_features.txt b/src/backend/catalog/sql_features.txt
index 4085a2d18d..e03e003187 100644
--- a/src/backend/catalog/sql_features.txt
+++ b/src/backend/catalog/sql_features.txt
@@ -230,8 +230,8 @@ F291	UNIQUE predicate			NO
 F292	UNIQUE null treatment			YES	
 F301	CORRESPONDING in query expressions			NO	
 F302	INTERSECT table operator			YES	
-F303	INTERSECT DISTINCT table operator			YES	
 F302	INTERSECT table operator	02	INTERSECT ALL table operator	YES	
+F303	INTERSECT DISTINCT table operator			YES	
 F304	EXCEPT ALL table operator			YES	
 F305	INTERSECT ALL table operator			YES	
 F311	Schema definition statement			YES	

view thread (5+ messages)  latest in thread

Message-ID: <98185277-F389-4B32-B0EB-D1D2DF52A8D0@yesql.se>
Permalink:  ../98185277-F389-4B32-B0EB-D1D2DF52A8D0@yesql.se/
Also on:    postgresql.org/message-id/98185277-F389-4B32-B0EB-D1D2DF52A8D0@yesql.se

 ·  · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: daniel@yesql.se, pgsql-docs@lists.postgresql.org, peter@eisentraut.org
  Subject: Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
  In-Reply-To: <98185277-F389-4B32-B0EB-D1D2DF52A8D0@yesql.se>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox