Re: Showing parallel status in \df+ - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Showing parallel status in \df+
Date
Msg-id 18057.1468165377@sss.pgh.pa.us
Whole thread Raw
In response to Re: Showing parallel status in \df+  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Showing parallel status in \df+  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Michael Paquier <michael.paquier@gmail.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [CF2016-9] Allow spaces in working path on tap-tests
Next
From: Netanel Katzburg
Date:
Subject: Re: Disable WAL completely - Performance and Persistency research