Hello!
> You should also test your client's response to the Pg server remaining
> up but becoming non-responsive (eg: failed disk array causes Pg backends
> to remain in uninterruptable disk I/O system calls in the kernel). A
> possibly good way to do this is to SIGSTOP the backend(s).
I haven't thought about it yet. It's possible the place where I should
use timeouts on the operations involving calls to PostgreSQL.
--
Sergey Samokhin
