Re: GEQO and join_collapse_limit correlation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: GEQO and join_collapse_limit correlation
Date: 2018-01-05 20:29:16
Message-ID: 12214.1515184156@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

=?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= <juanjo(dot)santamaria(at)gmail(dot)com> writes:
> In an environment with geqo_threshold=1 and join_collapse_limit=1, would
> the planner be GEQO exclusive (and syntactic)?

GEQO's only function, basically, is to search for the join order to use.
If you're constraining the join order completely with
join_collapse_limit=1 then forcing the GEQO path to be taken would just
add pointless overhead. (If it does anything at all ... I don't remember
the logic exactly but we might be bright enough not to bother with GEQO in
such a situation, regardless of geqo_threshold.)

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Juan José Santamaría Flecha 2018-01-06 11:31:51 Re: GEQO and join_collapse_limit correlation
Previous Message Juan José Santamaría Flecha 2018-01-05 20:17:06 Re: GEQO and join_collapse_limit correlation