Re: Psql patch to show access methods info

From: David Steele <david(at)pgmasters(dot)net>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Subject: Re: Psql patch to show access methods info
Date: 2020-03-02 13:33:04
Message-ID: 06e73feb-7ccf-a5ef-0843-79183ea30492@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Alexander,

On 1/21/20 5:37 PM, Alvaro Herrera wrote:
> On 2020-Jan-21, Alvaro Herrera wrote:
>
>> c) it would be damn handy if \dAf (maybe \dAf+) lists the datatypes that
>> each opfamily has opclasses for. Maybe make the output an array, like
>> {int4,int8,numeric,...} Something like [*] but somehow make it
>> prettier?
>
> Sorry, I forgot to copy-edit my text here: I said "make it prettier",
> but the query I submitted is already pretty enough ISTM; I had written
> that comment when I only had the array_agg() version, but then I changed
> it to string_agg() and that seems to have mostly done the trick. Maybe
> improve the format_type() bit to omit the quotes, if possible, but that
> doesn't seem a big deal.

The last CF for PG13 has now started. Do you know when you'll be able
to supply a new patch to address Álvaro's review?

Regards,
--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Arseny Sher 2020-03-02 13:37:04 Re: ERROR: subtransaction logged without previous top-level txn record
Previous Message Peter Eisentraut 2020-03-02 13:22:01 Silence compiler warnings with Python 3.9