From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | "Strauch, Sheldon" <sstrauch(at)enova(dot)com> |
Cc: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>, Michelle Schwan <mschwan(at)opentext(dot)com>, "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [EXTERNAL] - Re: pgAdmin IV |
Date: | 2019-06-05 14:50:34 |
Message-ID: | CA+OCxoy-fcvh1bqY0z3We9JSa_3064-cYCFfmrN+JF9p9ooknQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
I've rejected that I'm afraid, with the note:
=====
Bug 2880 refers to what happens if you execute "EXPLAIN SELECT..." as the
query, and that still works fine.
We use JSON output when you use the EXPLAIN *button*, because we need to
parse the output to render it in the graphical viewer. Whilst it's true
pgAdmin 3 parsed the output from the non-JSON EXPLAIN, it was complex code
that wasn't reliable or future-proof.
=====
In short, if you want to see multi-line, indented text plans, prepend
"EXPLAIN " to the query and run it. If you use the EXPLAIN button, the
returned data is in JSON format and is intended for graphical rendering.
On Wed, Jun 5, 2019 at 3:32 PM Strauch, Sheldon <sstrauch(at)enova(dot)com> wrote:
> Issue #4327 <https://redmine.postgresql.org/issues/4327> created.
>
> On Wed, Jun 5, 2019 at 12:27 AM Aditya Toshniwal <
> aditya(dot)toshniwal(at)enterprisedb(dot)com> wrote:
>
>> Hi Michelle,
>>
>> On Wed, Jun 5, 2019 at 12:42 AM Michelle Schwan <mschwan(at)opentext(dot)com>
>> wrote:
>>
>>> Aditya,
>>>
>>>
>>>
>>> That is not very intuitive! Why can’t the information be displayed?
>>> All of the other database tools for other databases allow this.
>>>
>> This can be done if we split the JSON data and show it in multiple rows.
>> Kindly raise a feature request here-
>> https://redmine.postgresql.org/projects/pgadmin4/issues/new
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__redmine.postgresql.org_projects_pgadmin4_issues_new&d=DwMFaQ&c=lEzKI_JJakPtcnbAQ6Q5xQ&r=3P3-5UqoQFsuwPHL1Gr-FtP4nR5GVvvXlP89XkF_Y4w&m=8zZt5HIwmsAu_V7PoSM9pCSMM-F8nyKZ9nklwYM3s-o&s=3ibwePEFSbRp8mLattu4u3GqYxPjLg-iLtdNU4yEp6c&e=>
>>
>>>
>>>
>>> Thanks,
>>>
>>> Michelle
>>>
>>>
>>>
>>> *From:* Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>
>>> *Sent:* Tuesday, June 04, 2019 10:50 AM
>>> *To:* Michelle Schwan <mschwan(at)opentext(dot)com>
>>> *Cc:* pgadmin-support lists.postgresql.org
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.postgresql.org&d=DwMFaQ&c=lEzKI_JJakPtcnbAQ6Q5xQ&r=3P3-5UqoQFsuwPHL1Gr-FtP4nR5GVvvXlP89XkF_Y4w&m=8zZt5HIwmsAu_V7PoSM9pCSMM-F8nyKZ9nklwYM3s-o&s=8guLseXWlVR6QzGAZayTiHbnygOxLH826F2Z6XchUjU&e=>
>>> <pgadmin-support(at)lists(dot)postgresql(dot)org>
>>> *Subject:* [EXTERNAL] - Re: pgAdmin IV
>>>
>>>
>>>
>>> You need to double click on the "[" cell. It is a json data.
>>>
>>>
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Aditya Toshniwal
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Jun 4, 2019, 20:10 Michelle Schwan <mschwan(at)opentext(dot)com> wrote:
>>>
>>> This is in all versions of pgAdmin IV.
>>>
>>>
>>>
>>> When generating an explain plan for a query, the data output only
>>> returns “[“. In pgAdmin III, there was a detailed output.
>>>
>>> It is easier to read the detailed data output than the explain pictures
>>> – I have to keep my mouse on the picture to read it, very inconvenient.
>>>
>>>
>>>
>>> Same query in pgAdmin III
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Michelle Schwan
>>>
>>> Database Architect
>>>
>>> mschwan(at)opentext(dot)com
>>>
>>> Phone: (519) 888 7111 ext 3241
>>>
>>> Website:
>>>
>>> www.opentext.com
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opentext.com_&d=DwMFaQ&c=lEzKI_JJakPtcnbAQ6Q5xQ&r=3P3-5UqoQFsuwPHL1Gr-FtP4nR5GVvvXlP89XkF_Y4w&m=8zZt5HIwmsAu_V7PoSM9pCSMM-F8nyKZ9nklwYM3s-o&s=c5S9yU0UPmoD_-iAc50_U2-4lagrne_wrU7cQ1BhHuU&e=>
>>>
>>>
>>>
>>> [image:
>>> http://mimage.opentext.com/alt_content/binary/images/emailsupport-logo-opentext.gif]
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opentext.com_2_email-2Dsignature-2Dlogo&d=DwMFaQ&c=lEzKI_JJakPtcnbAQ6Q5xQ&r=3P3-5UqoQFsuwPHL1Gr-FtP4nR5GVvvXlP89XkF_Y4w&m=8zZt5HIwmsAu_V7PoSM9pCSMM-F8nyKZ9nklwYM3s-o&s=B2kJl_1nLERpWAeaf4qoeUMHgk_myAcCRBStx6XUmbc&e=>
>>>
>>> This email message is confidential, may be privileged, and is intended
>>> for the exclusive use of the addressee. Any other person is strictly
>>> prohibited from disclosing or reproducing it. If the addressee cannot be
>>> reached or is unknown to you, please inform the sender by return email and
>>> delete this email message and all copies immediately.
>>>
>>>
>>>
>>>
>>
>> --
>> Thanks and Regards,
>> Aditya Toshniwal
>> Software Engineer | EnterpriseDB India | Pune
>> "Don't Complain about Heat, Plant a TREE"
>>
>
>
> --
>
> Look after your data, and your database will look after you. -- Simon Riggs
>
> Sheldon E. Strauch
> *Data Architect, Data Services *
> *O* 312-676-1556
> *M* 224-723-3878
>
> *Enova International, Inc.*
> *This transmission is confidential and may be privileged or proprietary.
> If you are not the intended recipient, you are not authorized to use the
> information in this transmission in any way. Please inform the sender
> immediately if you have received this transmission in error and permanently
> delete and destroy the original and any copies of the information.*
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2019-06-05 14:59:22 | Re: pgAdmin4 4.8 Kubuntu issues |
Previous Message | Alex Williams | 2019-06-05 14:46:45 | Re: centos 7 / pgadmin 4.7 |