Re: PG11 - Multiple Key Range Partition
| От | Rares Salcudean |
|---|---|
| Тема | Re: PG11 - Multiple Key Range Partition |
| Дата | |
| Msg-id | CAHp_FN3z2AMMOEA6houaE9w1_r43MYLnjN9ZPVyvpLErYRX0DA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: PG11 - Multiple Key Range Partition (David Rowley <david.rowley@2ndquadrant.com>) |
| Ответы |
Re: PG11 - Multiple Key Range Partition
|
| Список | pgsql-bugs |
Thank you guys for the quick response.
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?
By the way, keep it up, awesome work!
Rares
On Wed, Jul 10, 2019 at 1:07 PM David Rowley <david.rowley@2ndquadrant.com> wrote:
On Wed, 10 Jul 2019 at 21:02, Amit Langote <amitlangote09@gmail.com> wrote:
>
> On Wed, Jul 10, 2019 at 5:37 PM David Rowley
> > Thanks for making the test case. It is a bug. There's a problem in
> > match_clause_to_partition_key() where because
> > match_boolean_partition_clause() returns false for the "NOT b"
> > condition when comparing to the first partition key this causes the
> > function to return PARTCLAUSE_UNSUPPORTED which causes the calling
> > function to not bother trying to match that qual up to any other
> > partition key.
>
> Oops, indeed a bug. Should've returned PARTCLAUSE_NOMATCH there.
Here's a first draft fix for this, based on master.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-bugs по дате отправления: