On Tue, 19 Jul 2011 13:34:28 +0400 Anton Koldaev <[email protected]> wrote:
> Pgpool 3.0.1 / Postgres 8.4.5 / Online-recovery via PITR > Parameter: > recovery_timeout 300; > > Logs: > ERROR: pid 9444: wait_connection_closed: existing connections did not close > in 300 sec. > ERROR: pid 9444: start_recovery: timeover for waiting connection closed > > If I'll set recover_timeout to "0" recovery go 2nd stage successfull? No, "0" is not "disable". If you set recovery_timeout to 0, pgpool does time-out immediately. > What should happend to clients that *did not close their connections* and > are *not in idle*? > When do I need to use recovery_timeout > 0? You should set enough time which is required for the recovery to "recovery_timeout". You can use "client_idle_limit_in_recovery" to close connections forcibly. -- Toshihiro Kitagawa SRA OSS, Inc. Japan _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
