[pgpool-general: 8099] Re: Pg_stat_activity hung queries issue

[Tatsuo Ishii]

> Thanks for the explanation and fast response.
> 
> You mentioned the piggy internal queries, and I am trying to understand if
> what I saw is the right behaving.
> 
> I open a transaction, and my second statement was an Insert statement which
> was failed. In that case any other statements should be ignored until
> rollback. But after the Insert statement I did a select statement which
> triggers the piggy internal queries. In that case the first internal query
> was failed and because of that the connection was rebooted.
> 
> In that case this is fine ? Or not? Why piggy behave different  in that
> scenario where the internal query failed due to an earlier transaction
> error?

You mean following case for example?
(This is a session via pgpool.)

test=# begin;
BEGIN
test=*# insert into ttt values(1);
ERROR:  relation "ttt" does not exist
LINE 1: insert into ttt values(1);
                    ^
test=!# select 1;
ERROR:  current transaction is aborted, commands ignored until end of transaction block
test=!#

I think pgpool works as expected.

Best reagards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp