Skip site navigation (1) Skip section navigation (2)

Re: FDW state from plan time

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FDW state from plan time
Date: 2011-04-04 08:33:50
Message-ID: BANLkTi=+tSJEBu6dnF2YBB4vYxPo8-tuWw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sun, Apr 3, 2011 at 7:05 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> On 03.04.2011 19:38, Tom Lane wrote:
>>
>> Dave Page<dpage(at)pgadmin(dot)org>  writes:
>>>
>>> I can't help thinking I must be missing something obvious here, but is
>>> there any way to persist some data from PlanForeignScan to at least
>>> BeginForeignScan in an FDW? I'm aware of fdwplan->fdw_private, but at
>>> that needs to be copyObject compatible, it's not much use to me.
>
> If you have to, you can encapsulate arbitrary data in a bytea const.
>
>> Or you could use a hash of some other identifying information (perhaps
>> the OID of the foreign server would be sufficient ID for a connection?).
>
> Foreign server + user id, probably. That's what I would recommend in this
> case.

And database in some cases, but yes :-)

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Fujii MasaoDate: 2011-04-04 08:54:04
Subject: synchronous_commit and synchronous_replication Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Previous:From: Dave PageDate: 2011-04-04 08:31:31
Subject: Re: FDW state from plan time

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group