Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k2YZj-0007Kk-I2 for pgsql-docs@arkaria.postgresql.org; Mon, 03 Aug 2020 11:24:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k2YZi-00022a-4v for pgsql-docs@arkaria.postgresql.org; Mon, 03 Aug 2020 11:24:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k2YZh-00022T-VP for pgsql-docs@lists.postgresql.org; Mon, 03 Aug 2020 11:24:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k2YZb-0001zL-MS for pgsql-docs@postgresql.org; Mon, 03 Aug 2020 11:24:13 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 073BNmEV2266168; Mon, 3 Aug 2020 07:23:48 -0400 From: Tom Lane To: Michael Paquier cc: osdba , pgsql-docs@postgresql.org Subject: Re: Document "59.2. Built-in Operator Classes" have a clerical error? In-reply-to: <20200803074904.GO3317@paquier.xyz> References: <38d55061.9604.173b32c60ec.Coremail.mailtch@163.com> <20200803074904.GO3317@paquier.xyz> Comments: In-reply-to Michael Paquier message dated "Mon, 03 Aug 2020 16:49:04 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2266166.1596453828.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 03 Aug 2020 07:23:48 -0400 Message-ID: <2266167.1596453828@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Michael Paquier writes: > On Mon, Aug 03, 2020 at 03:14:56PM +0800, osdba wrote: >> "range_opsany range type&& &> &< >> << <@ -|- =3D @> @>"=EF=BC=8C exist= double "@>"=EF=BC=8C >> Should be "<@ @>" ? > Indeed, this needs to be improved. Another issue on the same page is > that point_ops lists the same operator three times, <@. Other index > pages don't seem to have any inconsistencies, fortunately. psql's handy new \dAo query clarifies things a bit: regression=3D# \dAo gist range_ops List of operators of operator families AM | Operator family | Operator | Strategy | Purpose = ------+-----------------+-------------------------+----------+--------- gist | range_ops | <<(anyrange,anyrange) | 1 | search gist | range_ops | &<(anyrange,anyrange) | 2 | search gist | range_ops | &&(anyrange,anyrange) | 3 | search gist | range_ops | &>(anyrange,anyrange) | 4 | search gist | range_ops | >>(anyrange,anyrange) | 5 | search gist | range_ops | -|-(anyrange,anyrange) | 6 | search gist | range_ops | @>(anyrange,anyrange) | 7 | search gist | range_ops | <@(anyrange,anyrange) | 8 | search gist | range_ops | =3D(anyrange,anyrange) | 18 | search gist | range_ops | @>(anyrange,anyelement) | 16 | search (10 rows) regression=3D# \dAo gist point_ops List of operators of operator families AM | Operator family | Operator | Strategy | Purpose = ------+-----------------+-------------------+----------+---------- gist | point_ops | <<(point,point) | 1 | search gist | point_ops | >>(point,point) | 5 | search gist | point_ops | ~=3D(point,point) | 6 | search gist | point_ops | <^(point,point) | 10 | search gist | point_ops | >^(point,point) | 11 | search gist | point_ops | <->(point,point) | 15 | ordering gist | point_ops | <@(point,box) | 28 | search gist | point_ops | <@(point,circle) | 68 | search gist | point_ops | <@(point,polygon) | 48 | search (9 rows) So I don't think it's a clerical error, but certainly showing these operators this way is none too helpful. Perhaps including the input types in this table (and its siblings elsewhere) would be a good thing. (Looking at these, I'm reminded anew that the sort ordering used by \dAo is still questionable ...) regards, tom lane