Re: pg 9.0, streaming replication, fail over and fail back strategies - Mailing list pgsql-general

From Kyle R. Burton
Subject Re: pg 9.0, streaming replication, fail over and fail back strategies
Date
Msg-id AANLkTin7v4V8YvVpX4Lzc0Jwq+wi9tWb8heW68wxMUoi@mail.gmail.com
Whole thread Raw
In response to Re: pg 9.0, streaming replication, fail over and fail back strategies  (Scott Marlowe <scott.marlowe@gmail.com>)
Responses Re: pg 9.0, streaming replication, fail over and fail back strategies
List pgsql-general
>> 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...


That is an excellent suggestion!  It just didn't occur to me.  I've
tried googling how to forward a port and am not having much success
(rinetd worked, but I feel like I should be able to get iptables to
work - do you have any pointers I could follow?)

Thanks again, this will most likely sove my vip binding issue.


Kyle

--
Twitter: @kyleburton
Blog: http://asymmetrical-view.com/
Fun: http://snapclean.me/

pgsql-general by date:

Previous
From: David Galkowski
Date:
Subject: change owner strange behavior
Next
From: "Joshua D. Drake"
Date:
Subject: Re: MySQL versus Postgres