Re: Oddity in tuple routing for foreign partitions

From: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, robertmhaas(at)gmail(dot)com, alvherre(at)alvh(dot)no-ip(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Oddity in tuple routing for foreign partitions
Date: 2018-04-26 06:44:17
Message-ID: 5AE17541.7000806@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(2018/04/26 15:39), Amit Langote wrote:
> On 2018/04/26 15:27, Etsuro Fujita wrote:
>> Here is a new version I'd like to propose for fixing this issue without
>> the former patch.

> Sorry, didn't notice this before sending my patch, which I also marked v7.
>
> It's a bit different than yours and has comments with excerpts from your
> earlier versions. See if you find it helpful.

OK, will review your version.

Best regards,
Etsuro Fujita

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2018-04-26 07:29:37 Re: Should we add GUCs to allow partition pruning to be disabled?
Previous Message Teodor Sigaev 2018-04-26 06:40:12 Re: Corrupted btree index on HEAD because of covering indexes