Re: Odd system-column handling in postgres_fdw join pushdown patch

From: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Odd system-column handling in postgres_fdw join pushdown patch
Date: 2016-04-15 16:16:10
Message-ID: CAFjFpRctesECUQSMirn2c58ZBvQ+Dr89txgZFWa8eii9GwoOig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 15, 2016 at 9:39 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Thu, Apr 14, 2016 at 7:49 AM, Ashutosh Bapat
> <ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> > BTW, I noticed that we are deparsing whole-row reference as ROW(list of
> > columns from local definition of foreign table), which has the same
> problem
> > with outer joins. It won't be NULL when the rest of the row from that
> > relation is NULL in an outer join. It too needs to be encapsulated in
> CASE
> > WHEN .. END expression. PFA patch with that fix included and also some
> > testcases for system columns as well as whole-row references.
>
> Good catch. But your test cases are no good because then we have OIDs
> hardcoded in the expected output. That means 'make installcheck' will
> fail, or if for any other reason the OID varies it will also fail.
> Committed your version with those test cases.
>
>
The testcases had tableoid::regclass which outputs the foreign table's
local name, which won't change across runs. Isn't that so?

--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2016-04-15 16:26:33 Re: GIN data corruption bug(s) in 9.6devel
Previous Message Robert Haas 2016-04-15 16:15:53 Re: EXPLAIN VERBOSE with parallel Aggregate