[Pgpool-general] replication/failover feature in Master/Slavemode

[Tatsuo Ishii]

No. Failover_command will be automatically executed by pgpool-II if
primary goes down. And you can have touch command to create the
trigger file in your failover_command. This should automatically
promote the standby.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> Thanks Tatsuo. So, does it mean with existing PG version (9.0), we need to 
> manually execute failover script (create trigger file) even when using pgpool?
> 
> 
> 
> 
> ________________________________
> From: Tatsuo Ishii <ishii at sraoss.co.jp>
> To: sandeeptt at yahoo.com
> Cc: Daniel.Crespo at l-3com.com; guillaume at lelarge.info; 
> pgpool-general at pgfoundry.org
> Sent: Fri, January 28, 2011 1:08:08 PM
> Subject: Re: [Pgpool-general] replication/failover feature in Master/Slavemode
> 
>> Yes, I'm aware that I need to create a trigger file (same as what is defined in 
>>
>> recovery.conf) to start the failover and promote the Standby to Primary. I have 
>>
>> tried this when I did not use pgpool and it worked fine. I thought, when pgpool 
>>
>> is in picture, it will execute the failver_command, when it detects that 
>>primary 
>>
>> is down. and since, the failover_command in my case is to "touch trigger file". 
>>
>> Shouldn't pgpool execute the failover_command here and create that file 
>> automatically?
> 
> Besides the problem that it's not easy to read and parse
> recovery.conf, creating trigger file might not be the only way to
> promote standby server forever. Actually currently PostgreSQL
> developers are discussing about "pg_ctl failover" command which will
> be a new way to promote standby in the next version of
> PostgreSQL. Pgpool-II is designed to be flexible to work with as many
> PostgreSQL version as possible. So we don't want to hard code "touch
> trigger file" in pgpool itself.
> 
>> I think, either pgpool is not able to detect that primary is down 
>> or it is unable to execute the failover_command. Am I missing to define 
>>anything 
>>
>> in the configuration file?