Re: Postgres_fdw join pushdown - wrong results with whole-row reference

From: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Postgres_fdw join pushdown - wrong results with whole-row reference
Date: 2016-07-01 14:16:23
Message-ID: CAFjFpRe+O8ziWBXwfrW-cOMKB0OywvTdqeQBjBM9TxTedHd0FQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 1, 2016 at 7:45 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Tue, Jun 28, 2016 at 8:20 AM, Ashutosh Bapat
> <ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> >> > postgres_fdw resets the search path to pg_catalog while opening
> >> > connection
> >> > to the server. The reason behind this is explained in deparse.c
> >> >
> >> > * We assume that the remote session's search_path is exactly
> >> > "pg_catalog",
> >> > * and thus we need schema-qualify all and only names outside
> >> > pg_catalog.
> >>
> >> Hmm. OK, should we revert the schema-qualification part of that
> >> commit, or just leave it alone?
> >
> > If we leave that code as is, someone who wants to add similar code later
> > would get confused or will be tempted to create more instances of
> > schema-qualification. I think we should revert the schema qualification.
>
> OK, done.
>

Thanks.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2016-07-01 14:20:52 Re: EXISTS clauses not being optimized in the face of 'one time pass' optimizable expressions
Previous Message Robert Haas 2016-07-01 14:15:00 Re: Postgres_fdw join pushdown - wrong results with whole-row reference