From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-performance@lists.postgresql.org
Subject: Re: Strange runtime partition pruning behaviour with 11.4
Date: Mon, 5 Aug 2019 09:29:33 +0200
Message-ID: <7cbc11eb-9c35-f844-ce9f-5820bf2a3a5c@gmx.net> (raw)
In-Reply-To: <14075.1564848353@sss.pgh.pa.us>
References: <29b2f4c6-987b-d364-2e1d-bbd479d06da2@gmx.net>
<cb89fa89-cef4-8510-2080-040712347b22@sqlexec.com>
<b9c05097-4c88-129a-545a-ab6997299b2b@a-kretschmer.de>
<9c55d578-bb70-d439-6450-abc291957ec3@gmx.net>
<84f4f721-2c1b-6a31-f10e-204af2c0e624@a-kretschmer.de>
<14075.1564848353@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: spam_eater@gmx.net, pgsql-performance@lists.postgresql.org
Subject: Re: Strange runtime partition pruning behaviour with 11.4
In-Reply-To: <7cbc11eb-9c35-f844-ce9f-5820bf2a3a5c@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox