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

From Robert Haas
Subject Re: elog() error, trying CURENT OF with foreign table
Date
Msg-id CA+TgmoYNf9zEPnrpfr5ywbejZwk7MWf9uf8JM7OLr4WXGk0KDw@mail.gmail.com
Whole thread Raw
In response to Re: elog() error, trying CURENT OF with foreign table  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: elog() error, trying CURENT OF with foreign table
List pgsql-hackers
On Fri, Apr 19, 2013 at 10:11 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Rushabh Lathia <rushabh.lathia@gmail.com> writes:
>> While trying out CURRENT OF with foreign table, ending up with error.
>
> Yeah, that's an unimplemented feature.
>
> In principle I think it could be made to work with postgres_fdw (since
> that uses CTID row identification), but I doubt that it'd be possible
> to promise that it works for every FDW.

So, should we just make that an
ereport(errcode(ERRCODE_FEATURE_NOT_SUPPORTED), ...) instead of
elog()?

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [GENERAL] currval and DISCARD ALL
Next
From: Adrian Klaver
Date:
Subject: Re: [GENERAL] currval and DISCARD ALL