Robert Haas writes:
> I think the only part of this that would be really brutal to try to
> represent is alternative join orders. I see no reasonable way for
> EXPLAIN to output useful information about what other join orders were
> considered and why they were not chosen; the only thing that see
On Fri, Sep 9, 2016 at 12:35 AM, Tom Lane wrote:
> Craig Ringer writes:
>> On 9 September 2016 at 01:40, Roger Pack wrote:
>>> Today's explain tells us what loops and scans were used, and relative
>>> costs, etc. It doesn't seem to tell *why* the planner elected to use
>>> what it did.
>
>> One
On 9/8/16 11:35 PM, Tom Lane wrote:
This isn't simple because there are often *lots* of variants. You
> don't just want to see the "top 10" candidate plans, because they're
> probably a bunch of small variants on the same plan; the ones you'll
> be interested in will probably be very different pl
On Thu, Sep 8, 2016 at 10:40 AM, Roger Pack wrote:
> My apologies if this was already requested before...
>
> I think it would be fantastic if postgres had an "explain the explain"
> option:
> Today's explain tells us what loops and scans were used, and relative
> costs, etc. It doesn't seem to
Craig Ringer writes:
> On 9 September 2016 at 01:40, Roger Pack wrote:
>> Today's explain tells us what loops and scans were used, and relative
>> costs, etc. It doesn't seem to tell *why* the planner elected to use
>> what it did.
> One thing that's been discussed here is to have a way to see
On 9 September 2016 at 01:40, Roger Pack wrote:
> My apologies if this was already requested before...
>
> I think it would be fantastic if postgres had an "explain the explain" option:
> Today's explain tells us what loops and scans were used, and relative
> costs, etc. It doesn't seem to tell *
My apologies if this was already requested before...
I think it would be fantastic if postgres had an "explain the explain" option:
Today's explain tells us what loops and scans were used, and relative
costs, etc. It doesn't seem to tell *why* the planner elected to use
what it did.
For instance
