Re: Bug in get_partition_for_tuple

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in get_partition_for_tuple
Date: 2017-03-28 00:57:09
Message-ID: c00d406a-24cc-4dec-ae59-a527b3ad6593@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2017/03/27 23:54, Robert Haas wrote:
> On Wed, Mar 22, 2017 at 4:00 AM, Amit Langote
> <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>> You're right, fixed that in the attached updated patch.
>>
>> Added this to the partitioning open items list, to avoid being forgotten
>> about.
>>
>> https://wiki.postgresql.org/wiki/PostgreSQL_10_Open_Items#Partitioning
>
> Thanks for adding it there. I'm making a sweep through that list now,
> or at least the parts of it that obvious pertain to my commits. This
> patch looks good, so committed.

Thanks.

Regards,
Amit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-03-28 00:58:53 Re: [COMMITTERS] pgsql: Clean up Perl code according to perlcritic
Previous Message Amit Langote 2017-03-28 00:56:26 Re: Partitioning vs ON CONFLICT