(2012/02/21 8:07), Shigeru Hanada wrote:
> Hm, agreed that isolation levels< REPEATABLE READ are not sufficient for
> pgsql_fdw's usage. I'll examine the example and fix pgsql_fdw.
Attached patch uses "safe" isolation level for remote transactions.
After this change, pgsql_fdw uses levels below:
local | remote
SERIALIZABLE | SERIALIZABLE
REPEATABLE READ | REPEATABLE READ
READ COMMITTED | REPEATABLE READ
READ UNCOMMITTED | REPEATABLE READ
Please review document of pgsql_fdw too.
In addition, I've removed #ifdef from options.c, so that we can specify
libpq options about SSL and Kerberos even if such feature has not been
configured on the environment where pgsql_fdw was built. This change
also avoids regression test failure on environment where any of
--with-openssl or --with-krb5 was specified for configure script.
In response to
pgsql-hackers by date
|Next:||From: Gianni Ciolli||Date: 2012-02-23 07:15:28|
|Subject: Re: Triggers with DO functionality|
|Previous:||From: Daniel Farina||Date: 2012-02-23 04:17:08|
|Subject: Re: Should we add crc32 in libpgport?|