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

From Tom Lane
Subject Re: Showing parallel status in \df+
Date
Msg-id 10659.1467988998@sss.pgh.pa.us
Whole thread Raw
In response to Re: Showing parallel status in \df+  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Showing parallel status in \df+  (Stephen Frost <sfrost@snowman.net>)
Re: Showing parallel status in \df+  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Friday, July 8, 2016, Michael Paquier <michael.paquier@gmail.com> wrote:
>> Fujii-san has reminded me of the fact that we do not show in \df+ the
>> parallel status of a function. The output of \df+ is already very
>> large, so I guess that any people mentally sane already use it with
>> the expanded display mode, and it may not matter adding more
>> information.
>> Thoughts about adding this piece of information?

> Seems like a good idea to me. It's going to be useful in debugging

If we're going to change \df+ at all, could I lobby for putting the Owner
column next to Security?  They're logically related, and not related to
Volatility which somehow got crammed between.  So I'm imagining the column
order as

Schema   | Name | Result data type | Argument data types |  Type  | Security | Owner | Volatility | Parallel | Language
|Source code | Description 
 

Or maybe Owner then Security.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: can we optimize STACK_DEPTH_SLOP
Next
From: Tom Lane
Date:
Subject: Re: Showing parallel status in \df+