| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, Ryan Murphy <ryanfmurphy(at)gmail(dot)com>, Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: \describe* |
| Date: | 2019-09-03 18:33:05 |
| Message-ID: | 20190903183305.GA20191@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Aug-01, Corey Huinker wrote:
> From all this, I have so far concluded:
>
> 1. There is real demand to be able to easily see the basic structure of
> tables, views, and indexes in a way that strikes a balance between detail
> and clutter.
That's great. That said, I'm not opposed to a DESCRIBE server-side
command, and others have shown some interest too. However, the thread
and commitfest entry at hand refer to a new psql command \describe,
which is completely unrelated. So I suggest we should close this CF
entry as Returned with Feedback, and wait until Corey comes back with a
server-side patch for DESCRIBE. I don't see the point of keeping a
\describe item alive if the patch we ultimately end up doing is
something completely different.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-09-03 18:38:56 | Re: Multivariate MCV list vs. statistics target |
| Previous Message | Fabien COELHO | 2019-09-03 18:10:37 | Re: refactoring - share str2*int64 functions |