MIME-Version: 1.0
In-Reply-To: <1e196503-3b9b-b16b-22a2-9e080faa4007@BlueTreble.com>
References: 
 <CAM9pMnPs3Jtw9nT7m9E7eH2E3xiExSR6mjmFQrZzoL__hwWxQQ@mail.gmail.com>
 <4b2f737a-ea37-35cd-012b-307ee1c9a584@BlueTreble.com>
 <11766.1468959038@sss.pgh.pa.us>
 <c693bae7-1779-d7f7-5485-2578974b02b9@BlueTreble.com>
 <15306.1469138384@sss.pgh.pa.us>
 <1e196503-3b9b-b16b-22a2-9e080faa4007@BlueTreble.com>
From: Robert Klemme <shortcutter@googlemail.com>
Date: Fri, 22 Jul 2016 10:37:20 +0200
Message-ID: 
 <CAM9pMnNKo6w_drc-xCjo=V-JT-z1y607nXxRfit6gG2LuBQAJg@mail.gmail.com>
Subject: Re: Seeing execution plan of foreign key constraint check?
To: Jim Nasby <Jim.Nasby@bluetreble.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
 pgsql-performance <pgsql-performance@postgresql.org>
Content-Type: text/plain; charset=UTF-8
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On Fri, Jul 22, 2016 at 12:14 AM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> On 7/21/16 4:59 PM, Tom Lane wrote:
>>>
>>> > As for function plans, ISTM that could be added to the PL handlers if
>>> > we
>>> > wanted to (allow a function invocation to return an array of explain
>>> > outputs).
>>
>> Where would you put those, particularly for functions executed many
>> times in the query?  Would it include sub-functions recursively?
>> I mean, yeah, in principle we could do something roughly like that,
>> but it's not easy and presenting the results intelligibly seems
>> almost impossible.
>
>
> Yeah, it'd certainly need to be handled internally in a
> machine-understandable form that got aggregated before presentation (or with
> non-text output formats we could provide the raw data). Or just punt and
> don't capture the data unless you're using an alternative output format.

I'd imagine the output to just list all "recursive" execution plans
executed probably along with indicators for how much IO and / or CPU
they were responsible for. The "recursive" plans could also be sorted
in decreasing order of total (i.e. across all individual invocations)
time spent so you see the most impacting plan first. All of that would
loose displaying calling relationships at the advantage of a simpler
presentation. I think, the relationship which statement / function
invoked with other could be determined by looking at statements /
functions. And I guess often it will be apparent from names already.

I am wondering what to do if the same statement has multiple execution
plans if that is possible in such a scenario. Present all the plans or
just the one with the highest impact? Show them next to each other so
the user is immediately aware that all these plans originated from the
same piece of SQL?

Kind regards

robert

-- 
[guy, jim, charlie].each {|him| remember.him do |as, often| as.you_can
- without end}
http://blog.rubybestpractices.com/


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance