Re: CALL stmt, ERROR: unrecognized node type: 113 bug - Mailing list pgsql-hackers

From Andres Freund
Subject Re: CALL stmt, ERROR: unrecognized node type: 113 bug
Date
Msg-id 20180209163049.fpknedffkllkqzeq@alap3.anarazel.de
Whole thread Raw
In response to Re: CALL stmt, ERROR: unrecognized node type: 113 bug  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: CALL stmt, ERROR: unrecognized node type: 113 bug  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2018-02-09 09:42:41 -0500, Tom Lane wrote:
> It doesn't look significantly different to me than the restriction
> that you can't have sub-selects in CHECK expressions, index
> expressions, etc.  Obviously we need a clean failure like you get for
> those cases.  But otherwise it's an OK restriction that stems from
> exactly the same cause: we do not want to invoke the full planner in
> this context (and even if we did, we don't want to use the full
> executor to execute the result).

+1


pgsql-hackers by date:

Previous
From: Claudio Freire
Date:
Subject: Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem
Next
From: Robert Haas
Date:
Subject: Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly