Re: Strange runtime partition pruning behaviour with 11.4
От
Thomas Kellerer
Тема
Re: Strange runtime partition pruning behaviour with 11.4
Дата
Msg-id
7cbc11eb-9c35-f844-ce9f-5820bf2a3a5c@gmx.net
Ответ на
Список
Дерево обсуждения
Strange runtime partition pruning behaviour with 11.4 Thomas Kellerer <spam_eater@gmx.net>
Re: Strange runtime partition pruning behaviour with 11.4 Sverre Boschman <s.r.boschman@gmail.com>
Re: Strange runtime partition pruning behaviour with 11.4 MichaelDBA <MichaelDBA@sqlexec.com>
Re: Strange runtime partition pruning behaviour with 11.4 Andreas Kretschmer <andreas@a-kretschmer.de>
Re: Strange runtime partition pruning behaviour with 11.4 Thomas Kellerer <spam_eater@gmx.net>
Re: Strange runtime partition pruning behaviour with 11.4 Andreas Kretschmer <andreas@a-kretschmer.de>
Re: Strange runtime partition pruning behaviour with 11.4 Tom Lane <tgl@sss.pgh.pa.us>
Re: Strange runtime partition pruning behaviour with 11.4 Thomas Kellerer <spam_eater@gmx.net>
Re: Strange runtime partition pruning behaviour with 11.4 MichaelDBA <MichaelDBA@sqlexec.com>
Tom Lane schrieb am 03.08.2019 um 18:05: > Yeah, I get the same plan with or without ANALYZE, too. In this example, > having the ANALYZE stats barely moves the rowcount estimates for > foo_bar_baz at all, so it's not surprising that the plan doesn't change. > (I do wonder how Thomas got a different outcome...) I don't know why either ;) I am using a JDBC based SQL tool to run that - I don't know if that matters. I just tried this script with Postgres 12 beta2 and there I do not get the initial plan with "never executed" (so the same behaviour as everybody else seems to have). If the reason why my initial plan is different than the "analyzed" plan lies in the configuration, I am happy to share my postgresql.conf if that is of any interest. Thomas
В списке pgsql-performance по дате отправления