| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:14:00 |
| Message-ID: | CA+TgmoYNf9zEPnrpfr5ywbejZwk7MWf9uf8JM7OLr4WXGk0KDw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 19, 2013 at 10:11 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2013-04-19 14:14:55 | Re: [GENERAL] currval and DISCARD ALL |
| Previous Message | Robert Haas | 2013-04-19 14:12:02 | Re: [GENERAL] currval and DISCARD ALL |