| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | koizumistr(at)minos(dot)ocn(dot)ne(dot)jp, pgsql-docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual |
| Date: | 2024-02-23 09:06:54 |
| Message-ID: | 98185277-F389-4B32-B0EB-D1D2DF52A8D0@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
> On 23 Feb 2024, at 06:36, PG Doc comments form <noreply(at)postgresql(dot)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
| Attachment | Content-Type | Size |
|---|---|---|
| f303.diff | application/octet-stream | 662 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 小泉 悟 | 2024-02-23 11:23:57 | Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual |
| Previous Message | PG Doc comments form | 2024-02-23 05:36:54 | incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual |