Re: "Multiple statements are an issue with pgPool-II in its replication mode" again

Le 22/11/2010 07:38, TAKATSUKA Haruka a écrit :
> [...]
> 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 any reason ?
> (e.g. There are many multiple-statements and they decide to give up ...)
>

No-one decided to give up on this. You should at least be able to connect.

> 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
>

I forgot pgPool when I commited this. I should probably add a comment in
this function :)

Will fix this.

> (*) pgpool-II execute multiple-SQLs at all backend nodes according to
> its feature and to run 'SELECT ... WHERE oid = 12345' generate diffrent
> answers. It causes an error.
>

Can you give us a complete example of this issue? if this is something
you get when modifying an object using pgAdmin's UI, it'll be hard to
do. pgAdmin relies a lot on multi-statements. But probably we can figure
a way to do this. I kind of did this for this patch :

http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=8dc53145d50ed2f65a112700c1390db79120f6d7

--
Guillaume
http://www.postgresql.fr
http://dalibo.com