Re: Odd behavior in foreign table modification (Was: Re: Optimization for updating foreign tables in Postgres FDW)

From: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Thom Brown <thom(at)linux(dot)com>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Odd behavior in foreign table modification (Was: Re: Optimization for updating foreign tables in Postgres FDW)
Date: 2016-02-05 04:03:36
Message-ID: 56B41F18.1040308@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2016/02/05 12:28, Robert Haas wrote:
> On Thu, Jan 28, 2016 at 7:36 AM, Etsuro Fujita
> <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> Attached is that version of the patch.
>>
>> I think that postgres_fdw might be able to insert a tableoid value in the
>> returned slot in e.g., postgresExecForeignInsert if AFTER ROW Triggers or
>> RETURNING expressions reference that value, but I didn't do anything about
>> that.

> Thanks. I went with the earlier version, but split it into two commits.

Thank you!

Best regards,
Etsuro Fujita

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-02-05 04:06:35 Re: count_nulls(VARIADIC "any")
Previous Message Etsuro Fujita 2016-02-05 04:01:06 Re: Optimization for updating foreign tables in Postgres FDW