| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: streaming replication trigger file |
| Date: | 2011-06-16 08:44:55 |
| Message-ID: | 4DF9C287.2000907@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 06/16/11 1:31 AM, AI Rumman wrote:
> When I manually create the C:\\pg\\stopreplication\\standby.txt' file,
> then it is working. That is, B is becoming the master.
> So, my question is, how this trigger file should be created so that B
> will become master automatically as soon as A goes down?
you need cluster management software, such as Heartbeat (on linux) or
Veritas Cluster Service (on various operating systems) configured to
detect system failure, and reconfigure the slave to be the master.
This software also generally is used to manage things like the shared IP
really really REALLY important is what to do when the failed original
master is brought back up. it can NOT be allowed to wake up thinking
its still a master since its lacking any updates since it went down,
instead it has to be reconfigured to be a new slave.
--
john r pierce N 37, W 122
santa cruz ca mid-left coast
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2011-06-16 09:15:38 | Re: Invalid byte sequence for encoding "UTF8": 0xedbebf |
| Previous Message | Pavel Stehule | 2011-06-16 08:41:40 | Re: Encryption For Specific Column- Where to store the key |