pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedincorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
5+ messages / 4 participants
[nested] [flat]
* incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
@ 2024-02-23 05:36 PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 5+ messages in thread
From: PG Doc comments form @ 2024-02-23 05:36 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: koizumistr@minos.ocn.ne.jp
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/features-sql-standard.html
Description:
In "D.1. Supported
Features"(https://www.postgresql.org/docs/current/features-sql-standard.html),
identifiers appear as following:
F302 INTERSECT table operator
F303 INTERSECT DISTINCT table operator
F302-02 INTERSECT ALL table operator
F304 EXCEPT ALL table operator
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
@ 2024-02-23 09:06 Daniel Gustafsson <daniel@yesql.se>
parent: PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 5+ messages in thread
From: Daniel Gustafsson @ 2024-02-23 09:06 UTC (permalink / raw)
To: koizumistr@minos.ocn.ne.jp, pgsql-docs <pgsql-docs@lists.postgresql.org>; +Cc: Peter Eisentraut <peter@eisentraut.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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
@ 2024-02-23 11:23 小泉 悟 <koizumistr@minos.ocn.ne.jp>
parent: Daniel Gustafsson <daniel@yesql.se>
0 siblings, 2 replies; 5+ messages in thread
From: 小泉 悟 @ 2024-02-23 11:23 UTC (permalink / raw)
To: Daniel Gustafsson <daniel@yesql.se>; +Cc: pgsql-docs <pgsql-docs@lists.postgresql.org>; Peter Eisentraut <peter@eisentraut.org>
Upon closer inspection, F305 is also "INTERSECT ALL table operator”.
Perhaps F302-02 would be unnecessary.
> 2024/02/23 18:06、Daniel Gustafsson <daniel@yesql.se>のメール:
>
>> 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
>
> <f303.diff>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
@ 2024-02-23 12:27 Daniel Gustafsson <daniel@yesql.se>
parent: 小泉 悟 <koizumistr@minos.ocn.ne.jp>
1 sibling, 0 replies; 5+ messages in thread
From: Daniel Gustafsson @ 2024-02-23 12:27 UTC (permalink / raw)
To: 小泉 悟 <koizumistr@minos.ocn.ne.jp>; +Cc: pgsql-docs <pgsql-docs@lists.postgresql.org>; Peter Eisentraut <peter@eisentraut.org>
> On 23 Feb 2024, at 12:23, 小泉 悟 <koizumistr@minos.ocn.ne.jp> wrote:
> Upon closer inspection, F305 is also "INTERSECT ALL table operator”.
> Perhaps F302-02 would be unnecessary.
The list is intended to reflect what's in the SQL:2023 standard, so whatever
the standard says we should too. I don't have a copy of the standard though so
I'll leave it to someone who does comment.
--
Daniel Gustafsson
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
@ 2024-02-23 13:59 Peter Eisentraut <peter@eisentraut.org>
parent: 小泉 悟 <koizumistr@minos.ocn.ne.jp>
1 sibling, 0 replies; 5+ messages in thread
From: Peter Eisentraut @ 2024-02-23 13:59 UTC (permalink / raw)
To: 小泉 悟 <koizumistr@minos.ocn.ne.jp>; Daniel Gustafsson <daniel@yesql.se>; +Cc: pgsql-docs <pgsql-docs@lists.postgresql.org>
On 23.02.24 12:23, 小泉 悟 wrote:
> Upon closer inspection, F305 is also "INTERSECT ALL table operator”.
> Perhaps F302-02 would be unnecessary.
Correct, F302-02 should have been deleted. I have fixed it, thanks.
>
>> 2024/02/23 18:06、Daniel Gustafsson <daniel@yesql.se>のメール:
>>
>>> 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
>>
>> <f303.diff>
>
>
>
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2024-02-23 13:59 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-02-23 05:36 incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual PG Doc comments form <noreply@postgresql.org>
2024-02-23 09:06 ` Daniel Gustafsson <daniel@yesql.se>
2024-02-23 11:23 ` 小泉 悟 <koizumistr@minos.ocn.ne.jp>
2024-02-23 12:27 ` Daniel Gustafsson <daniel@yesql.se>
2024-02-23 13:59 ` Peter Eisentraut <peter@eisentraut.org>
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