[Pgpool-general] db mismatch problem

[Longtime]

I have two case

case 1:
When I both update schema & data, and master and slave DB mismatch

pgpool alert this messages:
--
PGDMS2=# update tmp_data set lastmodified = '2009-05-15 00:00:00' where lastmodified <= '2009-05-14';
ERROR:  kind mismatch among backends. Possible last query was: "update tmp_data set lastmodified = '2009-05-
15 00:00:00' where lastmod
message contents do not agree with length in message type "E"
server closed the connection unexpectedly
      This probably means the server terminated abnormally
      before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.
--

this case the slave db will be stop query
and pcp_node_info result are
192.168.1.7 9999 2 1073741823.500000
192.168.1.8 9999 3 1073741823.500000

This is my expected value


Case 2:
When I only update data, and master and slave DB mismatch

pgpool alert this messages:
--
PGDMS2=# update profile set lastmodified = '2009-05-15 00:00:00'
PGDMS2-#  where lastmodified between '2008-12-15 00:00:00' and '2009-05-10 23:59:59';
ERROR:  pgpool detected difference of the number of inserted, updated or deleted tuples. Possible last query
was: "update profile set
message contents do not agree with length in message type "E"
--

this case the slave db will not be stop query
and pcp_node_info result still are
192.168.1.7 9999 2 1073741823.500000
192.168.1.8 9999 2 1073741823.500000

It's not my expected value
I hope slave db can be stop query when data mismatch


this is my pgpool.conf about replication mode + load_balance mode
replication_mode = true
load_balance_mode = true
replication_stop_on_mismatch = true
replicate_select = true
reset_query_list = 'ABORT; RESET ALL; SET SESSION AUTHORIZATION DEFAULT'


many thanks your help!