Re:Re: Document "59.2. Built-in Operator Classes" have a clerical error?

From: osdba <mailtch(at)163(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re:Re: Document "59.2. Built-in Operator Classes" have a clerical error?
Date: 2020-08-03 07:35:29
Message-ID: 3d755c97.9f2e.173b33f317e.Coremail.mailtch@163.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

you can see url: https://www.postgresql.org/docs/12/gist-builtin-opclasses.html
https://www.postgresql.org/docs/devel/gist-builtin-opclasses.html

you can see screen snapshot:

在 2020-08-03 11:43:53,"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> 写道:

On Sun, Aug 2, 2020 at 8:17 PM osdba <mailtch(at)163(dot)com> wrote:

hi all:

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

"range_opsany range type&& &> &< >> << <@ -|- = @> @>", exist double "@>",

Should be "<@ @>" ?

It helps to reference the current version of the page (or provide a url link) as that section seems to have migrated to Chapter 64 - though it is unchanged even on the main development branch.

The table itself is extremely difficult to read: it would be more easily readable if the font was monospaced, but its not.

I'm reasonably confident that the equal sign is part of the second-to-last operator while the lone @> is the final operator. Mostly I say this because GiST doesn't do straight equality so a lone equal operator isn't valid.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2020-08-03 07:39:11 Re: problem with RETURNING and update row movement
Previous Message Kyotaro Horiguchi 2020-08-03 07:20:40 Re: Is it worth accepting multiple CRLs?