On Sun, Apr 3, 2011 at 7:05 PM, Heikki Linnakangas <[email protected]> wrote: > On 03.04.2011 19:38, Tom Lane wrote: >> >> Dave Page<[email protected]> 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 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
