On Fri, Jul 22, 2022 at 1:20 PM Jacob Champion
wrote:
> On Wed, Jun 1, 2022 at 11:09 PM KAWAMOTO Masaya
> wrote:
> > That sounds a nice idea. But I don't think that postgres shows in the
> > EXPLAIN output why the plan is selected. Would it be appropriate to
> > show that GEQO is used in EXPLAIN
On Wed, Jun 1, 2022 at 11:09 PM KAWAMOTO Masaya wrote:
> That sounds a nice idea. But I don't think that postgres shows in the
> EXPLAIN output why the plan is selected. Would it be appropriate to
> show that GEQO is used in EXPLAIN output?
I'm reminded of Greenplum's "Optimizer" line in its EXPL
On Tue, 10 May 2022 18:49:54 +0530
Ashutosh Bapat wrote:
> If we add that information to EXPLAIN output, the user won't need
> access to server logs.
>
> May be we need it in both the places.
That sounds a nice idea. But I don't think that postgres shows in the
EXPLAIN output why the plan is se
If we add that information to EXPLAIN output, the user won't need
access to server logs.
May be we need it in both the places.
On Tue, May 10, 2022 at 6:35 AM KAWAMOTO Masaya wrote:
>
> Hi,
>
> During query tuning, users may want to check if GEQO is used or not
> to generate a plan. However, use
Hi,
During query tuning, users may want to check if GEQO is used or not
to generate a plan. However, users can not know it by simply counting
the number of tables that appear in SQL. I know we can know it by
enabling GEQO_DEBUG flag, but it needs recompiling, so I think it is
inconvenient.
So, I
