Hi, pgadmin-team.
This fix to execute "Set ..." and "SELECT ..." separately was
overwritten. Now pgAdmin-III 1.12.1 cannot connect pgpool-II
replication cluster. (*)
Is it has some reason ?
(e.g. There are many multiple-SQL and decide to give up ...)
2009-07-20 GL 1.12.0 Multiple statements are an issue with pgPool-II in
its replication mode.
* commitdiff: (fix multiple statements)
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=ef994af1e7a4bbd24f29fd99f452cbe315786286
* diff to current: (use multiple statements again)
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=blobdiff;f=pgadmin/db/pgConn.cpp;h=ea4aaa5b436f14494170c0994db23669ac953b00;hp=e4132817f6a896500689407829d75c2f92b95f57;hb=HEAD;hpb=ef994af1e7a4bbd24f29fd99f452cbe315786286
(*) pgpool-II execute multiple-SQLs in all backend nodes according to
its feature and to run 'SELECT ... WHERE oid = 12345' generate diffrent
answers. It causes an error.
______________________________________________________________________
TAKATSUKA Haruka [email protected] SRA OSS, Inc.
http://www.sraoss.co.jp/
--
Sent via pgadmin-support mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
