From: Bruce Momjian <bruce@momjian.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: osdba <mailtch@163.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Document "59.2. Built-in Operator Classes" have a clerical error?
Date: Mon, 24 Aug 2020 10:22:17 -0400
Message-ID: <20200824142217.GH26781@momjian.us> (raw)
In-Reply-To: <20200822185902.GA11024@alvherre.pgsql>
References: <2208818.1598117220@sss.pgh.pa.us>
<20200822185902.GA11024@alvherre.pgsql>
On Sat, Aug 22, 2020 at 02:59:02PM -0400, Alvaro Herrera wrote:
> 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.
I don't think it is worth it, plus we would need to adjust the docs if
system catalog layout changes. I think we just want something concise
and simple, but also accurate.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, michael@paquier.xyz, mailtch@163.com
Subject: Re: Document "59.2. Built-in Operator Classes" have a clerical error?
In-Reply-To: <20200824142217.GH26781@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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