On Mon, Aug 9, 2010 at 6:10 PM, Kyle R. Burton wrote:
> Hello,
>
> I'm new to the list and not even sure if this is the right place to be
> posting this...
>
> I've worked through the documentation for postgres 9.0 (beta2) and
> have successfully set up a master and hot slave configured with
> str
On Mon, Aug 9, 2010 at 6:10 PM, Kyle R. Burton wrote:
> 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 abi
On Tue, Aug 10, 2010 at 7:10 AM, Kyle R. Burton wrote:
> 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 ab
On Mon, 2010-08-09 at 19:32 -0400, Kyle R. Burton wrote:
> 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 pointer
>> 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?)
>
>
On Mon, Aug 9, 2010 at 4:10 PM, Kyle R. Burton 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
> i
