Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual - Mailing list pgsql-docs

From Peter Eisentraut
Subject Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
Date
Msg-id dd9710bb-d825-47ff-93f4-797550e240be@eisentraut.org
Whole thread Raw
In response to Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual  (小泉 悟 <koizumistr@minos.ocn.ne.jp>)
List pgsql-docs
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>
> 
> 
> 




pgsql-docs by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
Next
From: PG Doc comments form
Date:
Subject: Typos in dectoint() and dectolong() function's descriptions