thanks, i'll try it.<br><br><div class="gmail_quote">On Tue, Aug 14, 2012 at 12:04 PM, Nozomi Anzai <span dir="ltr"><<a href="mailto:anzai@sraoss.co.jp" target="_blank">anzai@sraoss.co.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I fixed this bug. Could you try again ?<br>
I tested by pgbench -M extended and a simple Java program.<br>
<br>
<a href="http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=e2a868905c99f8bc697a67e5790fd48fafe1cae2" target="_blank">http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=e2a868905c99f8bc697a67e5790fd48fafe1cae2</a><br>
<div class="HOEnZb"><div class="h5"><br>
<br>
> Thanks for the report. I reproduced it with "pgbench -S -M extended".<br>
> I'm fixing the bug soon.<br>
><br>
><br>
> > It seems as if pgpool does not pass through bind and execute steps of<br>
> > prepared statements anymore?<br>
> ><br>
> > i does think so, i can tell you from my debug log here :<br>
> ><br>
> > 2012-08-04 08:21:49 ERROR: pid 8897: Bind: cannot get parse message ""<br>
> > 2012-08-04 08:21:49 LOG: pid 8897: do_child: exits with status 1 due to<br>
> > error<br>
> ><br>
> > Karsten Düsterloh wrote :<br>
> > We were using pgpool-II 2.3.3 before<br>
> ><br>
> > does it work on production environment for Jabber server "openfire", which<br>
> > is written in Java ?<br>
> ><br>
> ><br>
> > On Tue, Aug 7, 2012 at 1:31 PM, Karsten Düsterloh<br>
> > <<a href="mailto:pgpool-general-ml@tal.de">pgpool-general-ml@tal.de</a>>wrote:<br>
> ><br>
> > > Hi!<br>
> > ><br>
> > > I think we experience the same problem.<br>
> > ><br>
> > > Soni Maula Harriz wrote:<br>
> > > > we are using pgpool-II 3.2.0 with replication mode and load balancing<br>
> > > > OS : Centos 6 (Pgpool and postgresql 8.4.9), Ubuntu (Postgresql 8.4.11)<br>
> > ><br>
> > > We're using pgpool-II 3.2.0 with replication mode and load balancing<br>
> > > under Debian 5 with Postgresql 8.3.16 servers as backends.<br>
> > > (We were using pgpool-II 2.3.3 before.)<br>
> > ><br>
> > > > application using JDBC 4<br>
> > > > we have a problem : the application cannot connect to the database<br>
> > ><br>
> > > We're using the Jabber server "openfire", which is written in Java and<br>
> > > indeed using JDBC (and proxool) for its database connection.<br>
> > ><br>
> > > > replication_mode = on<br>
> > > > insert_lock = on<br>
> > > > replicate_select = off<br>
> > > > insert_lock = on<br>
> > > > replication_stop_on_mismatch = on<br>
> > > > failover_if_affected_tuples_mismatch = on<br>
> > > > load_balance_mode = on<br>
> > > > ignore_leading_white_space = on<br>
> > > > white_function_list = ''<br>
> > > > black_function_list = 'nextval,setval'<br>
> > > > fail_over_on_backend_error = on<br>
> > ><br>
> > > Same here, remainder is usually set to default values.<br>
> > ><br>
> > > We can log into the database using psql with the openfire database<br>
> > > credentials just fine, but openfire can't.<br>
> > ><br>
> > > I've logged two startups of openfire in *postgresql*, one against pgpool<br>
> > > and failing and one against one the postgresql node directly and working.<br>
> > ><br>
> > > Failure via pgpool:<br>
> > > > 2012-08-07 08:08:01.798 CEST [17977] LOG: connection received: host=xxx<br>
> > > port=46636<br>
> > > > 2012-08-07 08:08:01.798 CEST [17978] LOG: connection received: host=xxx<br>
> > > port=46637<br>
> > > > 2012-08-07 08:08:01.798 CEST [17977] LOG: connection authorized:<br>
> > > user=jabber database=jabber<br>
> > > > 2012-08-07 08:08:01.798 CEST [17978] LOG: connection authorized:<br>
> > > user=jabber database=jabber<br>
> > > > 2012-08-07 08:08:01.833 CEST [17978] LOG: duration: 0.183 ms parse<br>
> > > <unnamed>: SHOW TRANSACTION ISOLATION LEVEL<br>
> > > > 2012-08-07 08:08:01.834 CEST [17978] LOG: disconnection: session time:<br>
> > > 0:00:00.035 user=jabber database=jabber host=xxx port=46637<br>
> > > > 2012-08-07 08:08:01.841 CEST [17977] LOG: duration: 0.294 ms parse<br>
> > > <unnamed>: SELECT 1<br>
> > > > 2012-08-07 08:08:01.843 CEST [17977] LOG: disconnection: session time:<br>
> > > 0:00:00.045 user=jabber database=jabber host=xxx port=46636<br>
> > > (Plus like 90 more tries of the same structure before openfire gives up.)<br>
> > ><br>
> > ><br>
> > > Working using postgresql directly:<br>
> > > > 2012-08-07 07:56:21.873 CEST [15940] LOG: connection received: host=yyy<br>
> > > port=36270<br>
> > > > 2012-08-07 07:56:21.873 CEST [15941] LOG: connection received: host=yyy<br>
> > > port=36271<br>
> > > > 2012-08-07 07:56:21.876 CEST [15941] LOG: connection authorized:<br>
> > > user=jabber database=jabber<br>
> > > > 2012-08-07 07:56:21.876 CEST [15940] LOG: connection authorized:<br>
> > > user=jabber database=jabber<br>
> > > > 2012-08-07 07:56:21.910 CEST [15940] LOG: duration: 0.206 ms parse<br>
> > > <unnamed>: SHOW TRANSACTION ISOLATION LEVEL<br>
> > > > 2012-08-07 07:56:21.910 CEST [15940] LOG: duration: 0.022 ms bind<br>
> > > <unnamed>: SHOW TRANSACTION ISOLATION LEVEL<br>
> > > > 2012-08-07 07:56:21.910 CEST [15940] LOG: duration: 0.042 ms execute<br>
> > > <unnamed>: SHOW TRANSACTION ISOLATION LEVEL<br>
> > > > 2012-08-07 07:56:21.924 CEST [15940] LOG: duration: 0.071 ms parse<br>
> > > <unnamed>: SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL READ<br>
> > > COMMITTED<br>
> > > > 2012-08-07 07:56:21.924 CEST [15940] LOG: duration: 0.007 ms bind<br>
> > > <unnamed>: SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL READ<br>
> > > COMMITTED<br>
> > > > 2012-08-07 07:56:21.924 CEST [15940] LOG: duration: 0.009 ms execute<br>
> > > <unnamed>: SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL READ<br>
> > > COMMITTED<br>
> > > > 2012-08-07 07:56:21.928 CEST [15941] LOG: duration: 0.257 ms parse<br>
> > > <unnamed>: SELECT 1<br>
> > > > 2012-08-07 07:56:21.928 CEST [15941] LOG: duration: 0.052 ms bind<br>
> > > <unnamed>: SELECT 1<br>
> > > > 2012-08-07 07:56:21.928 CEST [15941] LOG: duration: 0.014 ms execute<br>
> > > <unnamed>: SELECT 1<br>
> > > (etc. until minimum number of parallel connections are open, then normal<br>
> > > proceedings to read Jabber users, and so on.)<br>
> > ><br>
> > ><br>
> > > It seems as if pgpool does not pass through bind and execute steps of<br>
> > > prepared statements anymore?<br>
> > ><br>
> > ><br>
> > > Regards,<br>
> > ><br>
> > > Karsten Düsterloh<br>
> > > _______________________________________________<br>
> > > pgpool-general mailing list<br>
> > > <a href="mailto:pgpool-general@pgpool.net">pgpool-general@pgpool.net</a><br>
> > > <a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
> > ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Best Regards,<br>
> ><br>
> > Soni Maula Harriz<br>
> > Database Administrator<br>
> > PT. Data Aksara Sangkuriang<br>
><br>
><br>
> --<br>
> Nozomi Anzai<br>
> SRA OSS, Inc. Japan<br>
> _______________________________________________<br>
> pgpool-general mailing list<br>
> <a href="mailto:pgpool-general@pgpool.net">pgpool-general@pgpool.net</a><br>
> <a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
<br>
<br>
--<br>
Nozomi Anzai<br>
SRA OSS, Inc. Japan<br>
_______________________________________________<br>
pgpool-general mailing list<br>
<a href="mailto:pgpool-general@pgpool.net">pgpool-general@pgpool.net</a><br>
<a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Best Regards,<br><br>Soni Maula Harriz<br>Database Administrator<br>PT. Data Aksara Sangkuriang<br><br>