Re: elog() error, trying CURENT OF with foreign table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: elog() error, trying CURENT OF with foreign table
Date: 2013-04-19 14:46:43
Message-ID: 15878.1366382803@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabrízio de Royes Mello 2013-04-19 14:58:21 Re: [GENERAL] currval and DISCARD ALL
Previous Message Robert Haas 2013-04-19 14:29:48 Re: elog() error, trying CURENT OF with foreign table