> I guess, I was not clear. Because the same problem exists for > Pgpool-II. When pgpool forwards the message to the client, the client > will disconnect from pgpool. But if connection_life_time is not > reached (and by default this is unlimited) pgpool will not disconnect > from the postgres server. So the postgres server has not actually > achieved the intended goal, but the client still disconnected for no > benefit, only downsides.
Right. However, in many installations of Pgpool-II, health check is enabled. The health check process tries to connect to the PostgreSQL server which is in shutdown sequence, and fails because it will get "FATAL: the database system is shutting down" error. This will trigger a failover of PgpoolII and the pooled connections to backend are gone because all child process that holds the pools are killed, at least in some cases. Regards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp
