Re: Postgres_fdw join pushdown - wrong results with whole-row reference - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: Postgres_fdw join pushdown - wrong results with whole-row reference
Date
Msg-id 9c104785-0118-f467-f068-296d5f8b28e3@lab.ntt.co.jp
Whole thread Raw
In response to Re: Postgres_fdw join pushdown - wrong results with whole-row reference  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
List pgsql-hackers
On 2016/06/21 21:37, Ashutosh Bapat wrote:

>     How about using a system column eg, ctid, for the CASE WHEN
>     conversion; in Rushabh's example the reference to "r1" would be
>     converted with "CASE WHEN r1.ctid IS NOT NULL THEN ROW(r1.empno,
>     r1.ename, r1.job, r1.mgr, r1.hiredate, r1.sal, r1.comm, r1.deptno)
>     END".  IMO I think that that would be much simpler than Ashutosh's
>     approach.

> A foreign table can have a view, a regular table, another foreign table
> or a materialised view a its target. A view does not support any of the
> system columns, so none of them are available.

You are right.  Sorry for the noise.

Best regards,
Etsuro Fujita





pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Postgres_fdw join pushdown - wrong results with whole-row reference
Next
From: Craig Ringer
Date:
Subject: Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0