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

From Michael Paquier
Subject Re: Showing parallel status in \df+
Date
Msg-id CAB7nPqS-rb9t56auqj+7YnLNO+U0QxSA9jvW8x-eXS_CGG4yBg@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+  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Sat, Oct 1, 2016 at 9:47 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
>> On 9/28/16 2:59 PM, Alvaro Herrera wrote:
>>> My vote (which was not counted by Stephen) was to remove it from \df+
>>> altogether.  I stand by that.  People who are used to seeing the output
>>> in \df+ will wonder "where the heck did it go" and eventually figure it
>>> out, at which point it's no longer a problem.  We're not breaking
>>> anyone's scripts, that's for sure.
>>>
>>> If we're not removing it, I +0 support the option of moving it to
>>> footers.  I'm -1 on doing nothing.
>
>> I agree with everything Alvaro just said.
>
> Well, alternatively, can we get a consensus for doing that?  People
> did speak against removing PL source code from \df+ altogether, but
> maybe they're willing to reconsider if the alternative is doing nothing.
>
> Personally I'm on the edge of washing my hands of the whole thing...

Let's remove it and move on then. By looking again at this thread and
particularly https://www.postgresql.org/message-id/20160926190618.GH5148@tamriel.snowman.net
(thanks Stephen for the summary) that's where we are heading to.
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pg_upgade vs config
Next
From: Michael Paquier
Date:
Subject: Re: Showing parallel status in \df+