Re: Postgres undeterministically uses a bad plan, how to convince it otherwise? - Mailing list pgsql-general

From cen
Subject Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?
Date
Msg-id da2deef1-74fd-6745-e85d-37657dc16eb0@gmail.com
Whole thread Raw
In response to Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
On 16/02/2023 17:07, David G. Johnston wrote:

No, the planner may not cause execution.  While I could imagine extending EXPLAIN to somehow retrieve and maybe even try alternative plans that have been fully constructed today I'm not holding my breath.

There is little reason for the project to give any real weight to "assuming the query to be immutable".  We do want to fix the planner to behave better if it is mis-behaving, otherwise you do have access to cost parameters, and potentially other planner toggles if you've truly run into an intractable problem.

David J.

Fair on both points. I didn't know planner toggles existed, I'll play with that.

pgsql-general by date:

Previous
From: Andreas Joseph Krogh
Date:
Subject: Sv: PostgreSQL configuration in a VM
Next
From: Marc Millas
Date:
Subject: Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?