Re: Odd system-column handling in postgres_fdw join pushdown patch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Odd system-column handling in postgres_fdw join pushdown patch
Date
Msg-id CA+TgmoYm8zbrhrd7tRuMP9+5T0ihN+vW23OsveWbS7XquJg=JQ@mail.gmail.com
Whole thread Raw
In response to Re: Odd system-column handling in postgres_fdw join pushdown patch  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Responses Re: Odd system-column handling in postgres_fdw join pushdown patch  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
List pgsql-hackers
On Wed, Apr 13, 2016 at 11:21 PM, Etsuro Fujita
<fujita.etsuro@lab.ntt.co.jp> wrote:
>>> 2. When a join is pushed down, deparse system columns using something
>>> like "CASE WHEN r1.* IS NOT NULL THEN 0 END", except for the table OID
>>> column, which gets deparsed with the table OID in place of 0.  This
>>> delivers the correct behavior in the presence of outer joins.
>> I think that that would cause useless data transfer for such culumns.
>> Why not set values locally for such columns?

Because that doesn't work properly when there are outer joins
involved.  I see no other way of doing that correctly that's anywhere
near as simple as this.

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



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Support for N synchronous standby servers - take 2
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Support for N synchronous standby servers - take 2