Re: PG11 - Multiple Key Range Partition
David Rowley <david.rowley@2ndquadrant.com>
From: David Rowley <david.rowley@2ndquadrant.com>
To: Rares Salcudean <rares.salcudean@takeofflabs.com>
Cc: Amit Langote <amitlangote09@gmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2019-07-12T03:54:01Z
Lists: pgsql-bugs
On Wed, 10 Jul 2019 at 23:14, Rares Salcudean <rares.salcudean@takeofflabs.com> wrote: > Which would be the simplest way to "import/apply" this fix locally for me? Do I have to wait until the new version is released? That's really up to you. I'd at least wait for the patch to be committed though. From then, if you're comfortable patching and building yourself then you could get the fix sooner. Otherwise, there should be a release around the end of September. I'm about to take a more serious look at the patch I posted a few days ago. -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
Fix RANGE partition pruning with multiple boolean partition keys
- cfde23493938 13.0 landed
- 30a268ed2e29 12.0 landed
- 757f1baa8c13 11.5 landed