| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(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-10 15:42:57 |
| Message-ID: | 18057.1468165377@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
>> - Reordering the columns, I'd suggest as follows):
>> -- Schema
>> -- Name
>> -- Result data type
>> -- Argument data types
>> -- Type
>> -- Language
>> -- Volatility
>> -- Parallel
>> -- Owner
>> -- Security
>> -- ACL
>> -- Source code
>> -- Description
If we're keeping the "Source code" column, I'd be inclined to keep
"Language" adjacent to that. When thinking of a function as a black
box, both language and source code are implementation details; but
all the other properties listed here are of interest anyway.
(Of course, if we were to get rid of "Source code", the point
would be moot ...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2016-07-10 17:56:01 | PSA: Systemd will kill PostgreSQL |
| Previous Message | Tom Lane | 2016-07-10 14:52:25 | Re: [CF2016-9] Allow spaces in working path on tap-tests |