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

Re: pgsql_fdw, FDW for PostgreSQL server

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Shigeru Hanada *EXTERN*" <shigeru(dot)hanada(at)gmail(dot)com>,"Kohei KaiGai" <kaigai(at)kaigai(dot)gr(dot)jp>
Cc: "Etsuro Fujita" <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Robert Haas" <robertmhaas(at)gmail(dot)com>,"Hitoshi Harada" <umi(dot)tanuki(at)gmail(dot)com>,"Martijn van Oosterhout" <kleptog(at)svana(dot)org>,"PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql_fdw, FDW for PostgreSQL server
Date: 2012-02-16 15:15:55
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers
Shigeru Hanada wrote:
> Thanks for the review.  Attached patches are revised version, though
> only fdw_helper_v5.patch is unchanged.

Two questions:
- Is it on purpose that you can specify all SSL client options
  except "sslcompression"?
- Since a rescan is done by rewinding the cursor, is it necessary
  to have any other remote isolation level than READ COMMITED?
  There is only one query issued per transaction.

Laurenz Albe

In response to


pgsql-hackers by date

Next:From: Marko KreenDate: 2012-02-16 15:17:25
Subject: Re: Speed dblink using alternate libpq tuple storage
Previous:From: Robert HaasDate: 2012-02-16 14:09:03
Subject: Re: Should we add crc32 in libpgport?

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