Re: [sqlsmith] Failed assertion in postgres_fdw/deparse.c:1116

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [sqlsmith] Failed assertion in postgres_fdw/deparse.c:1116
Дата
Msg-id CA+TgmoYRZTwCH27UY4kJNoAAnGAY86RO+J1PFo+KpecCHR3i_Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [sqlsmith] Failed assertion in postgres_fdw/deparse.c:1116  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Ответы Re: [sqlsmith] Failed assertion in postgres_fdw/deparse.c:1116  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Список pgsql-hackers
On Thu, Jun 16, 2016 at 7:05 AM, Etsuro Fujita
<fujita.etsuro@lab.ntt.co.jp> wrote:
> ISTM that a robuster solution to this is to push down the ft1-ft2-ft3 join
> with the PHV by extending deparseExplicitTargetList() and/or something else
> so that we can send the remote query like:
>
> select ft1.a, (ft3.a IS NOT NULL) from (ft1 inner join ft2 on ft1.a = ft2.a)
> left join ft3 on ft1.a = ft3.a

I completely agree we should have that, but not for 9.6.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [GENERAL] PgQ and pg_dump
Следующее
От: Robert Haas
Дата:
Сообщение: Re: forcing a rebuild of the visibility map