[pgpool-general: 1578] Re: pgpool 3.2.3 node gets down after some hours of work.

[Tatsuo Ishii]

>> May be this will help:
>> 
>> 2013-04-07 11:48:52 LOG:   pid 9785: do_child: exits with status 1 due to
>> error
>> 2013-04-07 11:48:52 LOG:   pid 9760: pool_read_kind: error message from 2
>> th backend:canceling statement due to conflict with recovery
>> 2013-04-07 11:48:53 LOG:   pid 9767: detect_stop_postmaster_error:
>> detect_error error
>> 2013-04-07 11:48:53 LOG:   pid 9767: detect_postmaster_down_error returns
>> error on backend 2. Going to close this session.
>> 2013-04-07 11:59:28 LOG:   pid 9651: do_child: exits with status 1 due to
>> error
> 
> Those themselves do not related to node down or fail over.
> 
> Anyway are yo still using 3.2.3? or upgraded to 3.2-stable?

Oops. You already told me you upgraded to 3.2-stable.

> Also do yo see this kind of message?
> 
> 	 pool_log("postmaster on DB node %d was shutdown by administrative command", i);
> 
> If you see this, someone used pg_terminate_backend(). This makes
> pgpool confuses because it returned exactly same error code as
> postmaster shutdown. So pgpool will detach the node where the function
> issued.

More thought. If fail_over_on_backend_error = on, pgpool will trigger
fail over when read/write errors are detected on the socket to
PostgreSQL connection. Turning this off may help for an environment
where network connection is flakey.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp