Re: Showing parallel status in \df+

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, 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-08 14:43:18
Message-ID: 10659.1467988998@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Friday, July 8, 2016, Michael Paquier <michael(dot)paquier(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-07-08 14:48:17 Re: Showing parallel status in \df+
Previous Message Tom Lane 2016-07-08 14:32:20 Re: can we optimize STACK_DEPTH_SLOP