Re: Accounting for between table correlation
| От | Alexander Stoddard |
|---|---|
| Тема | Re: Accounting for between table correlation |
| Дата | |
| Msg-id | CADDNc-CA0Y=1Urh3nLGy8nZf7V8cDrHcD1V6dpgzfLkJsPtz=w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Accounting for between table correlation (Michael Lewis <mlewis@entrata.com>) |
| Ответы |
Re: Accounting for between table correlation
|
| Список | pgsql-general |
On Tue, Jan 19, 2021 at 2:47 PM Michael Lewis <mlewis@entrata.com> wrote:
On Fri, Jan 15, 2021 at 3:27 PM Alexander Stoddard <alexander.stoddard@gmail.com> wrote:I am doing nothing to specify the optimizer. Do I have configurable options in that regard? I was unaware of them.Read up on join_collapse_limit and geqo.Note that you can set these values within your session to check and even just run explain [query] to check if the plan that would be used varies.
Thank you for this. I can get different plans by changing the different parameters, but if the output of EXPLAIN VERBOSE tells me geqo planning specifically is being used I'm not seeing it. Is there a way to see in the explain plan if geqo was used?
В списке pgsql-general по дате отправления: