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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, osdba <mailtch(at)163(dot)com>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Document "59.2. Built-in Operator Classes" have a clerical error?
Date: 2020-08-22 03:19:07
Message-ID: 20200822031907.GA12615@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On 2020-Aug-21, Bruce Momjian wrote:

> On Mon, Aug 3, 2020 at 04:49:04PM +0900, Michael Paquier wrote:
> > On Mon, Aug 03, 2020 at 03:14:56PM +0800, osdba wrote:
> > > "range_opsany range type&& &> &< >> << <@ -|- = @> @>", exist double "@>",
> > >
> > > 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.
>
> I decided to remove the duplicates and just add "(multiple)" after
> operators that have multiple system table entries; patch attached.

Now that we can point people to psql's \dAo, do we really need to have
these tables at all?

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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message David G. Johnston 2020-08-22 03:41:54 Re: Create a Foreign Table for PostgreSQL CSV Logs
Previous Message David G. Johnston 2020-08-22 02:42:35 Re: Procedures