From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: osdba <mailtch@163.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Document "59.2. Built-in Operator Classes" have a clerical error?
Date: Tue, 4 Aug 2020 14:56:51 +0900
Message-ID: <20200804055651.GC2091@paquier.xyz> (raw)
In-Reply-To: <2266167.1596453828@sss.pgh.pa.us>
References: <38d55061.9604.173b32c60ec.Coremail.mailtch@163.com>
<20200803074904.GO3317@paquier.xyz>
<2266167.1596453828@sss.pgh.pa.us>
On Mon, Aug 03, 2020 at 07:23:48AM -0400, Tom Lane wrote:
> 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.
Ah, thanks. I did not consider the psql shortcut. I agree that
including the input types would be a good idea. But just doing that
may not be enough IMO as the character policy used on our website for
the HTML docs makes that harder to parse. What if we switched the
third column to have one line per operator with its input type, and
use morerows to show the full set of indexable operators one opclass
is associated with? Contrary to wait events, those tables don't
change much. I am wondering as well if we should consider mentioning
\dAo on all those pages, say at the bottom of each table listing the
opclasses.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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: michael@paquier.xyz, tgl@sss.pgh.pa.us, mailtch@163.com
Subject: Re: Document "59.2. Built-in Operator Classes" have a clerical error?
In-Reply-To: <20200804055651.GC2091@paquier.xyz>
* 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