Re: elog() error, trying CURENT OF with foreign table - Mailing list pgsql-hackers

From Tom Lane
Subject Re: elog() error, trying CURENT OF with foreign table
Date
Msg-id 15878.1366382803@sss.pgh.pa.us
Whole thread Raw
In response to Re: elog() error, trying CURENT OF with foreign table  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: elog() error, trying CURENT OF with foreign table
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> My main concern was actually whether we ought to be detecting this
> earlier in the process, before it gets as far as the executor.

Yeah, that might be an appropriate response too.  The executor is
coded so cavalierly because it expects the planner to have replaced
the CURRENT OF node with something executable.  As things now stand,
whether that happens or not depends in part on the behavior of FDWs,
so maybe we'd better have the planner check whether it happened.
I'm not sure though if there's any suitably-painless place to do it.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: elog() error, trying CURENT OF with foreign table
Next
From: Fabrízio de Royes Mello
Date:
Subject: Re: [GENERAL] currval and DISCARD ALL