Re: Wrong cost estimation for foreign tables join withuse_remote_estimate disabled
От
Amit Langote
Тема
Re: Wrong cost estimation for foreign tables join withuse_remote_estimate disabled
Дата
Msg-id
0cf348a1-9d97-eb7f-954e-18e593c48a75@lab.ntt.co.jp
Ответ на
Список
Дерево обсуждения
Wrong cost estimation for foreign tables join withuse_remote_estimate disabled Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled Tom Lane <tgl@sss.pgh.pa.us>
Re: Wrong cost estimation for foreign tables join withuse_remote_estimate disabled Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Wrong cost estimation for foreign tables join with use_remote_estimatedisabled Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
Re: Wrong cost estimation for foreign tables join withuse_remote_estimate disabled Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Re: Wrong cost estimation for foreign tables join with use_remote_estimatedisabled Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
Re: Wrong cost estimation for foreign tables join withuse_remote_estimate disabled Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
Re: Wrong cost estimation for foreign tables join withuse_remote_estimate disabled Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Wrong cost estimation for foreign tables join withuse_remote_estimate disabled Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
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
В списке pgsql-hackers по дате отправления
