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

From Michael Paquier
Subject Re: Showing parallel status in \df+
Date
Msg-id CAB7nPqR5jYV6SgCywedSF-Fm83=ApXq+Ppjpcu2AD+Mtt3S2cA@mail.gmail.com
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+  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Jul 9, 2016 at 8:12 AM, Michael Paquier
<michael.paquier@gmail.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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [CF2016-9] Allow spaces in working path on tap-tests
Next
From: Tom Lane
Date:
Subject: Re: [CF2016-9] Allow spaces in working path on tap-tests