| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Masao Fujii <masao(dot)fujii(at)gmail(dot)com> |
| Subject: | Re: Showing parallel status in \df+ |
| Date: | 2016-07-12 16:45:57 |
| Message-ID: | 20160712164557.GX4028@tamriel.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > Agreed. I don't have any issue with "Language", really, but I agree
> > that "Source code" makes the output pretty ridiculous. I also liked the
> > idea of changing the name to "internal name" or something along those
> > lines, rather than having it be "source code", if we keep the column for
> > C/internal functions. Keeping is as "source code" wouldn't be accurate.
>
> It's sounding to me like we have consensus on this proposal to further
> change \df+ to replace the "Source code" column with "Internal name",
> which is prosrc for C and internal-language functions but NULL otherwise.
>
> If I've not heard objections by tomorrow I'll go make that change.
>
> Are we satisfied with telling people to use \sf to see the source code
> for a PL function? Or should there be another variant of \df that
> still provides source code?
I don't see the point in having a \df variant be the same as what \sf
is. I could possibly see extending \sf in some way, if there are things
that it doesn't currently do that \df does (and those things are
useful).
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2016-07-12 16:53:30 | pg_basebackup wish list |
| Previous Message | Tom Lane | 2016-07-12 16:40:34 | Re: GiST index build versus NaN coordinates |