Re: Wrong cost estimation for foreign tables join with use_remote_estimatedisabled - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: Wrong cost estimation for foreign tables join with use_remote_estimatedisabled
Date
Msg-id 5B2CCEA0.6080507@lab.ntt.co.jp
Whole thread Raw
In response to Re: Wrong cost estimation for foreign tables join withuse_remote_estimate disabled  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
(2018/06/22 18:49), Amit Langote wrote:
> On 2018/06/22 18:15, Etsuro Fujita wrote:
>> I'd vote for #2.  One idea for that is to introduce CREATE FOREIGN INDEX
>> to have information on remote indexes on the local side, which I proposed
>> before.  I have been putting it on hold since then, though.
>
> Sorry to hijack this thread, but I'd like to say that CREATE FOREIGN INDEX
> would be nice, as that would also let us lift certain restrictions on
> partitioned table indexes [1].

Agreed.  I think that would be useful to support INSERT ... ON CONFLICT 
fully not only on single foreign tables but partitioned tables 
containing foreign partitions.

Best regards,
Etsuro Fujita


pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: Incorrect errno used with %m for backend code
Next
From: Ashutosh Bapat
Date:
Subject: Re: Wrong cost estimation for foreign tables join withuse_remote_estimate disabled