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

From Tom Lane
Subject Re: Odd system-column handling in postgres_fdw join pushdown patch
Date
Msg-id 27356.1460583211@sss.pgh.pa.us
Whole thread Raw
In response to Re: Odd system-column handling in postgres_fdw join pushdown patch  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Odd system-column handling in postgres_fdw join pushdown patch  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> 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.

Um, why would that be necessary?  Surely the correct things will happen
on the far end without that, if it's implementing the same join semantics
as the local query would have.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <
Next
From: Tatsuo Ishii
Date:
Subject: Re: Incomplete startup packet errors