From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Jonathan S. Katz <jkatz@postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Poll: are people okay with function/operator table redesign?
Date: Mon, 13 Apr 2020 19:50:52 -0400
Message-ID: <20200413235052.GA25649@alvherre.pgsql> (raw)
In-Reply-To: <aa9cb88f-798e-fbe6-6d9b-a64fef67f5cb@postgresql.org>
On 2020-Apr-13, Jonathan S. Katz wrote:
> On 4/13/20 7:02 PM, Jonathan S. Katz wrote:
> > Perhaps a counterproposal: We eliminate the content in the leftmost
> > "function column, but leave that there to allow the function name /
> > signature to span the full 3 columns. Then the rest of the info goes
> > below. This will also compress the table height down a bit.
>
> An attempt at a "POC" of what I'm describing (attached image).
>
> I'm not sure if I 100% like it, but it does reduce the amount of
> information we're displaying but conveys all the details (and matches
> what we have in the previous version).
Ooh, this seems a nice idea -- the indentation seems to be sufficient to
tell apart entries from each other. Your point about information
reduction refers to the fact that we no longer keep the unadorned name
but only the signature, right? That seems an improvement to me now that
I look at it.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, jkatz@postgresql.org, tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
Subject: Re: Poll: are people okay with function/operator table redesign?
In-Reply-To: <20200413235052.GA25649@alvherre.pgsql>
* 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