From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: postgres_fdw behaves oddly |
Date: | 2014-09-02 09:55:27 |
Message-ID: | 5405940F.4040906@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
(2014/09/01 20:15), Etsuro Fujita wrote:
> While working on [1], I've found that postgres_fdw behaves oddly:
>
> postgres=# create foreign table ft (a int) server loopback options
> (table_name 't');
> CREATE FOREIGN TABLE
> postgres=# select tableoid, * from ft;
> tableoid | a
> ----------+---
> 16400 | 1
> (1 row)
>
> postgres=# select tableoid, * from ft where tableoid = 16400;
> tableoid | a
> ----------+---
> (0 rows)
> I think that one simple way of fixing such issues would be
> to consider unsafe to send to the remote a qual that contains any system
> columns.
I noticed the previous patch has overdone it. Attached is an updated
version of the patch.
Thanks,
PS:
> [1] https://commitfest.postgresql.org/action/patch_view?id=1386
I'll update the patch in [1] on top of this version.
Best regards,
Etsuro Fujita
Attachment | Content-Type | Size |
---|---|---|
fdw_sys_col_v2.patch | text/x-patch | 2.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2014-09-02 09:56:34 | Re: PL/pgSQL 2 |
Previous Message | Álvaro Hernández Tortosa | 2014-09-02 09:52:34 | Re: PL/pgSQL 2 |