From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | 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-08 12:27:34 |
Message-ID: | CAA4eK1+79x9_MDWNEWAiMaF_heDK5NU_u8BWp2JBxP3caA9rpw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 8, 2016 at 5:27 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Fri, Jul 8, 2016 at 4:04 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> On Friday, July 8, 2016, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
>>>
>>> Hi all,
>>>
>>> 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
>
> Okay. Here we go. I named the column for the parallel information "Parallelism".
>
Another option could be to name it as Parallel Mode. We are using
that in the description of "Parallel" in "Create Function"
documentation.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2016-07-08 13:24:41 | Re: Reviewing freeze map code |
Previous Message | Marco Nenciarini | 2016-07-08 12:22:35 | Re: [BUGS] BUG #14230: Wrong timeline returned by pg_stop_backup on a standby |