Re: verbose cost estimate

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: verbose cost estimate
Date: 2019-12-09 23:31:39
Message-ID: 20191209233139.sx43slauynijqzkx@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 09, 2019 at 05:40:40PM -0500, Tom Lane wrote:
>Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
>> ... Perhaps a path-specific struct, referenced
>> from the path and built only with verbose explain would be fine?
>
>How would that work, given that the planner doesn't know whether its
>output is going to get explained? With features like the plan cache
>and auto_explain in mind, it's very hard to see how you avoid having
>to save the information always.
>

I don't know, but my assumption is that this information would be needed
only very rarely. So maybe we could pass a flag enabling this to the
planner when executed from explain, and disable storing the plan in the
plan cache, or something. And the additional info would be only
available when explicitly requested using an extra EXPLAIN option.

So for example auto_explain would not really show this (or it might get
an extra option, with additional overhead).

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2019-12-09 23:44:09 xact_start for walsender & logical decoding not updated
Previous Message Tomas Vondra 2019-12-09 23:25:46 Re: verbose cost estimate