pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #16569: Document "59.2. Built-in Operator Classes" have a clerical error
2+ messages / 2 participants
[nested] [flat]

* BUG #16569: Document "59.2. Built-in Operator Classes" have a clerical error
@ 2020-08-03 03:28  PG Bug reporting form <noreply@postgresql.org>
  0 siblings, 1 reply; 2+ messages in thread

From: PG Bug reporting form @ 2020-08-03 03:28 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: mailtch@163.com

The following bug has been logged on the website:

Bug reference:      16569
Logged by:          osdba
Email address:      mailtch@163.com
PostgreSQL version: 9.5.0
Operating system:   all
Description:        

In Document "Table 59-1. Built-in GiST Operator Classes":

"range_ops	any range type	&& &> &< >> << <@ -|- = @> @>",

 double "@> @>",  I think should be "<@ @>" .

all version document have same clerical error.



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: BUG #16569: Document "59.2. Built-in Operator Classes" have a clerical error
@ 2020-08-04 17:11  Tomas Vondra <tomas.vondra@2ndquadrant.com>
  parent: PG Bug reporting form <noreply@postgresql.org>
  0 siblings, 0 replies; 2+ messages in thread

From: Tomas Vondra @ 2020-08-04 17:11 UTC (permalink / raw)
  To: mailtch@163.com; pgsql-bugs@lists.postgresql.org

On Mon, Aug 03, 2020 at 03:28:27AM +0000, PG Bug reporting form wrote:
>The following bug has been logged on the website:
>
>Bug reference:      16569
>Logged by:          osdba
>Email address:      mailtch@163.com
>PostgreSQL version: 9.5.0
>Operating system:   all
>Description:
>
>In Document "Table 59-1. Built-in GiST Operator Classes":
>
>"range_ops	any range type	&& &> &< >> << <@ -|- = @> @>",
>
> double "@> @>",  I think should be "<@ @>" .
>
>all version document have same clerical error.
>

I agree this is rather confusing, but I don't think it's a bug ...

I'd bet the reason why we have '@> @>' and not '<@ @>' is that those for
different argument types. GiST range_ops has

    @>(anyrange,anyrange)
    <@(anyrange,anyrange)
    @>(anyrange,anyelement)

But we only show the first and third one, because the <@ is commutator
for the first one.

We have a similar thing for point_ops where we have <@ three times, but
those are for different combinations of point, box and circle types.

It's confusing, though. I wonder if we should do one or more of these
changes:

(1) include accepted argument types

(2) only list distinct oprname (so not printing <@ twice)

(3) include commutators (so printing both <@ and @>) 

(4) link to https://www.postgresql.org/docs/12/functions-range.html
     which already has alll these additional details


regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2020-08-04 17:11 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-08-03 03:28 BUG #16569: Document "59.2. Built-in Operator Classes" have a clerical error PG Bug reporting form <noreply@postgresql.org>
2020-08-04 17:11 ` Tomas Vondra <tomas.vondra@2ndquadrant.com>

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