[Pgpool-general] Suggestion for Failover on Master/Slave Streaming Replication

[Tatsuo Ishii]

> Using Master/Slave with Streaming Replication and Hot Standby, on
> Failover, I think it would be a good idea to have pgpool stop handling
> connections until new master becomes writable. Maybe, the application
> should handle this, but we don't want the application check if the
> database is writable every time an INSERT, UPDATE, or DELETE is about to
> be run. Any workaround? I'm tempted to add a sleep in pgpool when a
> failover happens, before handling new connections to the new master, in
> order for the new master to become writable (by touching the
> corresponding file) and be able to service the clients without giving
> them errors.

Interesting thought. The obvious idea would be add a config directive
which allow pgpool to wait N seconds before the new primary server is
ready for accepting connections from clients. More smart idea would be
that pgpool checks new primary is available or not before accepting
new connections. Better idea?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp