| 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: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled |
| Date: | 2018-06-22 10:25:36 |
| Message-ID: | 5B2CCEA0.6080507@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2018-06-22 10:30:16 | Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled |
| Previous Message | Ashutosh Sharma | 2018-06-22 10:15:33 | Re: Incorrect errno used with %m for backend code |