[pgpool-general: 476] Re: abnormal behavior pgpool on drop

[Tatsuo Ishii]

> I have pgpool-II version 3.1.3 installed and three db postgresql 9.1.3 in
> streaming replication. When i try to drop database i see this in pgpool log:
> 
> 2012-05-21 15:01:48 LOG:   pid 15484: pool_send_and_wait: Error or notice
> message from backend: : DB node id: 1 backend pid: 6769 statement: DROP
> DATABASE xxx; message: database "xxx" is being accessed by other users
> 2012-05-21 15:02:20 LOG:   pid 26326: postmaster on DB node 1 was shutdown
> by administrative command
> 2012-05-21 15:02:20 LOG:   pid 26326: degenerate_backend_set: 1 fail over
> request from pid 26326
> 2012-05-21 15:02:20 LOG:   pid 4975: starting degeneration. shutdown host
> 10.141.2.54(5432)
> 2012-05-21 15:02:20 LOG:   pid 4975: Restart all children
> 2012-05-21 15:02:20 LOG:   pid 4975: execute command:
> /etc/pgpool.d/failover.sh 1 10.141.2.54 5432 /var/lib/postgresql/9.1/main 0
> 10.141.2.53 0 1
> 2012-05-21_15:02:20 failover: Master failed at 10.141.2.54 (0). New master
> is 10.141.2.53 (0)
> 2012-05-21_15:02:20 failover: New master start triggered.
> 
> Why pgpool initiated failover procedure on statement drop database? I add
> drop statement in black_function_list may be this helps me.

Why do you think drop database initiated failover? The failover
happend 32 seconds after drop database error.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp