From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 12:15:09 |
Message-ID: | CAB7nPqR5jYV6SgCywedSF-Fm83=ApXq+Ppjpcu2AD+Mtt3S2cA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Jul 9, 2016 at 8:12 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> So to sum up:
> - Add "Parallel" column
> - Add ACLs
> - 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
> Or by thema, 1) General info, 2) specificity (volatility, parallel,
> type), 3) Ownership.
> And regarding "source code", I think that's useful for debugging.
Giving the attached, including doc clarifications and column
reshuffling with translatable state set up as well.
--
Michael
Attachment | Content-Type | Size |
---|---|---|
psql-function-describe-v2.patch | application/x-patch | 3.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-07-10 14:52:25 | Re: [CF2016-9] Allow spaces in working path on tap-tests |
Previous Message | Michael Paquier | 2016-07-10 11:28:16 | Re: [CF2016-9] Allow spaces in working path on tap-tests |