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

Alvaro Herrera <alvherre@2ndquadrant.com>

From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>, Michael Paquier <michael@paquier.xyz>, osdba <mailtch@163.com>, pgsql-docs@postgresql.org
Date: 2020-08-22T18:59:02Z
Lists: pgsql-docs
On 2020-Aug-22, Tom Lane wrote:

> If you don't want to go all the way and list the operators with their
> input types, maybe we should just do what the OP thought was correct
> and delete the duplicate operator names.  It's already the case that
> the table isn't telling you exactly which input types the operators
> accept, so why not be a little bit fuzzier?

Well, if we're going to have a table, let's have a useful table.  What's
wrong with using the same contents \dAo shows? It seemed reasonable
enough to me.

Now of course I would suggest that other client programs such as pgAdmin
ought to display what \dAo shows too ;-)

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



Commits

  1. doc: Rework tables for built-in operator classes of index AMs