Re: Problem, partition pruning for prepared statement with IS NULL clause.
Sergei Glukhov <s.glukhov@postgrespro.ru>
From: Sergei Glukhov <s.glukhov@postgrespro.ru>
To: David Rowley <dgrowleyml@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2023-10-11T09:09:36Z
Lists: pgsql-hackers
Hi, Thanks for fixing this! I verified that issues are fixed. On 10/11/23 11:50, David Rowley wrote: > I'm aiming to commit these as two separate fixes, so I'm going to go > look again at the first one and wait to see if anyone wants to comment > on this patch in the meantime. Regarding test case for the first patch, the line 'set plan_cache_mode = 'force_generic_plan';' is not necessary since cache mode is set at the top of the test. On the other hand test scenario can silently be loosed if someone set another cache mode somewhere upper. As you mentioned earlier it's worth maybe adding the test for run-time partition pruning. Regards, Gluh
Commits
-
Fix runtime partition pruning for HASH partitioned tables
- 2759924f33a6 11.22 landed
- 3cc0c25172b2 12.17 landed
- 890a73ba3ac0 13.13 landed
- d26f33c32436 14.10 landed
- 1e81d3e6e0a0 15.5 landed
- 595db9e9cc41 16.1 landed
- d9e46dfb78ab 17.0 landed
-
Fix incorrect step generation in HASH partition pruning
- 07f261b3172d 11.22 landed
- cd259de50ac5 12.17 landed
- 45c4b2a3aa72 13.13 landed
- cd15bff4814b 14.10 landed
- 916adc7c50bb 15.5 landed
- 6352f1627641 16.1 landed
- f0c409d9c7a6 17.0 landed