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

From Michael Paquier
Subject Re: Showing parallel status in \df+
Date
Msg-id CAB7nPqTW0+1r5O0+j-ibeZ4HX0jyR7=Tnc5ai-m1RfQ4Q-F43A@mail.gmail.com
Whole thread Raw
In response to Re: Showing parallel status in \df+  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Showing parallel status in \df+  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Jul 11, 2016 at 12:42 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

OK, no objections to that. And this gives the attached.

> (Of course, if we were to get rid of "Source code", the point
> would be moot ...)

I still think that having source code is useful for debugging, so I
left it out. Note for the committer who will perhaps pick up this
patch: I left out "Source Code", but feel free to remove it if you
think the contrary. It is easier to remove code than adding it back.
--
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: Michael Paquier
Date:
Subject: Re: Issue with bgworker, SPI and pgstat_report_stat