Hello, I still have issues (empty results) with using load balancing and hot streaming replication with pgpool 3.0.x and PostgreSQL 9.0.2.
In 9.0.4 release notes it says: Use better SQLSTATE error codes for hot standby conflict cases (Tatsuo Ishii and Simon Riggs) All retryable conflict errors now have an error code that indicates that a retry is possible. Also, session closure due to the database being dropped on the master is now reported as ERRCODE_DATABASE_DROPPED, rather than ERRCODE_ADMIN_SHUTDOWN, so that connection poolers can handle the situation correctly. Could that resolve the issues, i.e. does pgpool then issue a retry by itself? Kind regards, Tom Spivey _______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
