[pgpool-general: 3477] failover on write failure (no disk space left)?

[Aistis Zen]

Hello

I managed to go past failover scenarios with introduction of failback
scripts. All the "normal" tests like failover and failback are working, so
I went further and tested out-of-order scenario with the master suddenly
not having enough disk space. What happened is.. nothing. My script keeps
on trying to write and pgpool reporting:

Feb 20 17:02:47 slave pgpool[16626]: DB node id: 1 backend pid: 17243
statement: BEGIN
Feb 20 17:02:47 slave pgpool[16626]: DB node id: 0 backend pid: 3689
statement: INSERT into demo.test(uid) values(37501);
Feb 20 17:02:47 slave pgpool[16626]: pool_send_and_wait: Error or notice
message from backend: : DB node id: 0 backend pid: 3689 statement: INSERT
into demo.test(uid) values(37501); message: could not extend file
"base/24675/24681": No space left on device

Shouldn't it assume that the backend has an issue and initiate a failover
in this case? Is there anything to be configured in pgpool, which could
catch such exception? I know it does SELECT's to check availability, but it
doesn't seem to care if the master database is no longer writable.


Thank you!
Aistis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20150220/9162d0d6/attachment.htm>