>>> What we like to have is the ability to: >>> - Treat the error code got back from pg_terminate_backend (or the kill >>> command) as a regular disconnect >> >> It isn't possible without changing PostgreSQL itself. > > Can you please explain why? If we kill -INT a backend postgres > process, it doesn't take the whole database cluster down, it shouldn't > take the whole pool down either. The fact that it does is a bug in > pg_pool IMO.
The problem is PostgreSQL returns exactly the same error code when postmaster goes down. See: http://archives.postgresql.org/pgsql-hackers/2010-05/msg00629.php for more details. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
