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

From: "Kyle R(dot) Burton" <kyle(dot)burton(at)gmail(dot)com>
To: Scott Marlowe <scott(dot)marlowe(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 23:32:58
Message-ID: AANLkTin7v4V8YvVpX4Lzc0Jwq+wi9tWb8heW68wxMUoi@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mabry Tyson 2010-08-10 00:23:46 Win Server 2003: postgres can't logon
Previous Message Scott Marlowe 2010-08-09 22:17:14 Re: pg 9.0, streaming replication, fail over and fail back strategies