Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
Cc: 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 09:49:46
Message-ID: 0cf348a1-9d97-eb7f-954e-18e593c48a75@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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].

Thanks,
Amit

[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=4eaa5372754

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2018-06-22 09:55:38 Re: [HACKERS] GUC for cleanup indexes threshold.
Previous Message Michael Paquier 2018-06-22 09:39:54 Re: Possible bug in logical replication.