Re: PlaceHolderVars in pushed down child-join cause error

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PlaceHolderVars in pushed down child-join cause error
Date: 2018-02-22 15:06:42
Message-ID: CA+TgmoaAtAwEXPoFADZpLmG5XCOXMmOapd4+Uw8AUrGArDJdZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 22, 2018 at 7:41 AM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> postgres_fdw isn't expected to push down joins with placeholder vars.
> But the check for that in foreign_join_ok() only considers
> joinrel->relids. For a child-join relids contains the child relids but
> PlaceHolderInfo refers to the top parent's relids. Hence postgres_fdw
> tries to push down a child-join with PlaceHolderVars in it and fails
> with error "unsupported expression type for deparse: 198". 198 being
> T_PlaceHolderVar.
>
> The fix is to use joinrel->top_parent_relids for a child-join.
> Attached patch for the same.

Committed, but I changed the formatting, because as you had it,
pgindent would have mangled it. While I was at it, I tweaked the
wording of the comment a bit.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-02-22 15:09:37 Re: Incorrect grammar
Previous Message Robert Haas 2018-02-22 14:32:32 Re: pgsql: Avoid valgrind complaint about write() of uninitalized bytes.