Re: pg 9.0, streaming replication, fail over and fail back strategies

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: "Kyle R(dot) Burton" <kyle(dot)burton(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg 9.0, streaming replication, fail over and fail back strategies
Date: 2010-08-09 22:17:14
Message-ID: AANLkTinHBiSwV2sOPxtANHT7UbogjCpf81tDw5vvb-nz@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Aug 9, 2010 at 4:10 PM, Kyle R. Burton <kyle(dot)burton(at)gmail(dot)com> wrote:
> Hello,
> After I had moved the VIP from the master to the slave, I had to
> restart (not just reload) the postgres daemon to get it to start

Not surprising as you say.

> Is there any way to get PostgreSQL to bind to a new ip address and
> interface without actually shutting it down?  If it could, would I
> need to break all the current (read only) client connections to get
> them to reconnect and have the ability to write?  (am I confused about
> this?)

I wonder if you could have pg on a steady ip and use iptables to
forward traffic there after a failover...

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kyle R. Burton 2010-08-09 23:32:58 Re: pg 9.0, streaming replication, fail over and fail back strategies
Previous Message Kyle R. Burton 2010-08-09 22:10:47 pg 9.0, streaming replication, fail over and fail back strategies