From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
---|---|
To: | Rares Salcudean <rares(dot)salcudean(at)takeofflabs(dot)com> |
Cc: | Amit Langote <amitlangote09(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PG11 - Multiple Key Range Partition |
Date: | 2019-07-12 03:54:01 |
Message-ID: | CAKJS1f_7tiQ5xBt3KqXUk-8yG-ddjtjYo1VB8VwweyK6ZoiEXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, 10 Jul 2019 at 23:14, Rares Salcudean
<rares(dot)salcudean(at)takeofflabs(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-07-12 04:23:37 | Re: PG11 - Multiple Key Range Partition |
Previous Message | Peter Geoghegan | 2019-07-12 03:31:37 | Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« |