Re: Instability of partition_prune regression test results
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Langote <amitlangote09@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-09-28T17:34:19Z
Lists: pgsql-hackers
Amit Langote <amitlangote09@gmail.com> writes: > On Sat, Sep 28, 2019 at 12:59 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Amit Langote <amitlangote09@gmail.com> writes: >>> Isn't the point of using ANALYZE here to show that the exec-param >>> based run-time pruning is working (those "never executed" strings)? >> Hm. Well, if you want to see those, we could do it as attached. > Perfect, thanks. OK, pushed that way. regards, tom lane
Commits
-
Rely on plan_cache_mode to force generic plans in partition_prune test.
- d52eaa094847 13.0 landed
-
Improve stability of partition_prune regression test.
- 9de7ea6aca5a 12.0 landed
- 4ea03f3f4eba 13.0 landed
- 0baa55655e05 11.6 landed