[Pgpool-general] Problem with replication mode!!!

[Lazaro Ruben Garcia Martinez]

Hello every one. 
I have this problem. 
I have one database in two nodes, I use Pgpool-II version 2.3.3. 
This database has one table, in the first node (master) there is a table with one record and in the other node this table there isn't any record, but when I execute a Select or Update over this table, the secondary node is never degenerate (failover is not perform). 

I tested this problem in Pgpool-II version 3.0.1 and I have the same situation. 

pgpool.conf of Pgpool-II version 2.3.3. 
replication_stop_on_mismatch = true 

pgpool.conf of Pgpool-II version 2.3.3. 
replication_stop_on_mismatch = true 
failover_if_affected_tuples_mismatch = true 

The documentation of pgpool says: 
failover_if_affected_tuples_mismatch 

When set to true, if a backend returns number of affected tuples by INSERT/UPDATE/DELETE different between the backends, the backends that differ from most frequent result set are degenerated. If set to false, the session is terminated and the backends are not degenerated. Default is false. replication_stop_on_mismatch 

When set to true, if a backend returns packet kind different between the backends, the backends that differ from most frequent result set are degenerated. Typical use case is the SELECT statement is part of a transaction and replicate_select is set to true, and SELECT returns diffrent number of rows among backends. Other than SELECT statement might trigger this though. For example, a backend succeeded in an UPDATE, while others failed. Also please note that pgpool does NOT examine content of records returned from SELECT. If set to false, the session is terminated and the backends are not degenerated. Default is false. 
Anyone knows why is it? 

Regards. 
Thank you very much for your time. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pgfoundry.org/pipermail/pgpool-general/attachments/20101105/61e71acc/attachment.html>