Re: Declarative partitioning - another take

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Amit Langote <amitlangote09(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dmitry Ivanov <d(dot)ivanov(at)postgrespro(dot)ru>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Erik Rijkers <er(at)xs4all(dot)nl>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers-owner(at)postgresql(dot)org
Subject: Re: Declarative partitioning - another take
Date: 2016-12-19 03:00:29
Message-ID: 262107e8-c506-6b34-f38a-2e5a1710a48e@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On 2016/12/17 11:32, Amit Langote wrote:
> On Sat, Dec 17, 2016 at 1:07 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Fri, Dec 16, 2016 at 3:02 AM, Amit Langote
>> <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>> Aside from the above, I found few other issues and fixed them in the
>>> attached patches. Descriptions follow:
>>
>> To avoid any further mistakes on my part, can you please resubmit
>> these with each patch file containing a proposed commit message
>> including patch authorship information, who reported the issue, links
>> to relevant discussion if any, and any other attribution information
>> which I should not fail to include when committing?
>
> I think it's a good advice and will keep in mind for any patches I
> post henceforth.
>
> In this particular case, I found all the issues myself while working
> with some more esoteric test scenarios, except the first patch (1/7),
> where I have mentioned in the description of the patch in the email,
> that there were independent reports of the issue by Tomas Vondra and
> David Fetter.

Here are updated patches including the additional information.

Thanks,
Amit

Attachment Content-Type Size
0001-Invalidate-the-parent-s-relcache-after-partition-cre-2.patch text/x-diff 3.5 KB
0002-Change-how-RelationGetPartitionQual-and-related-code-2.patch text/x-diff 11.4 KB
0003-Refactor-tuple-routing-setup-code-2.patch text/x-diff 10.7 KB
0004-Fix-a-bug-of-insertion-into-an-internal-partition-2.patch text/x-diff 8.6 KB
0005-Fix-oddities-of-tuple-routing-and-TupleTableSlots-2.patch text/x-diff 5.4 KB
0006-Make-ExecConstraints-emit-the-correct-row-in-error-m-2.patch text/x-diff 11.9 KB
0007-Add-some-more-tests-for-tuple-routing-2.patch text/x-diff 5.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2016-12-19 03:03:45 Re: Measuring replay lag
Previous Message Andres Freund 2016-12-19 02:57:39 Retire src/backend/port/dynloader/linux.c ?