Re: FDW: possible resjunk columns in AddForeignUpdateTargets

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "rdunklau(at)gmail(dot)com" <rdunklau(at)gmail(dot)com>
Subject: Re: FDW: possible resjunk columns in AddForeignUpdateTargets
Date: 2013-11-06 15:01:46
Message-ID: 27966.1383750106@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> writes:
> I have a question concerning the Foreign Data Wrapper API:
> I find no mention of this in the documentation, but I remember that
> you can only add a resjunk column that matches an existing attribute
> of the foreign table and not one with an arbitrary name or
> definition.

> Ist that right?

I don't recall such a limitation offhand. It's probably true that
you can't create Vars that don't match some declared column of the
table, but that doesn't restrict what you put into resjunk columns
AFAIR.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2013-11-06 15:11:16 Recent matview push broken with -DCLOBBER_CACHE_ALWAYS
Previous Message Peter Eisentraut 2013-11-06 14:59:22 Re: UNION ALL on partitioned tables won't use indices.