rease on planning times if I turn geqo = off.
I guess what I'm trying to show is that, in very particular cases, GEQO may
harm planning times, that's why I felt a little disclaimer could be useful.
I'm not sure what else I can add here.
Regards,
Carlo
On Tue, Oct 28, 2025 at 11:
QO ineffective / not the right approach.
In my view, this "addendum" also leaves some room to these other
considerations without compromising readability.
I'd like to hear your thoughts on that.
Regards,
Carlo
On Mon, Oct 27, 2025 at 10:24 PM Tomas Vondra wrote:
> On 10/27/25
Hello experts,
Recently, we've been encountering poor query plans on our database workload.
We've successfully diagnosed the cause as reaching the default limit of 8
for join_collapse_limit.
We've already dealt with the situation successfully. However, I've been
discussing with some colleagues th
