From: | Edson Richter <richter(at)simkorp(dot)com(dot)br> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL 9.0 and asynchronous replication through VPN |
Date: | 2011-12-03 03:01:33 |
Message-ID: | 4ED9910D.80907@simkorp.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Indeed, there is a log message. My problem was that I missed to add
"listen_address='*'" to my postgresql.conf!
Hope this helps others in future.
Regards,
*Edson Carlos Ericksson Richter*
/SimKorp Informática Ltda/
Fone: (51) 3366-7964
Celular: (51)9318-9766/(51) 8585-0796
Embedded Image
Em 30-11-2011 14:41, Edson Richter escreveu:
> Em 30-11-2011 11:17, John DeSoi escreveu:
>> On Nov 30, 2011, at 5:02 AM, Edson Richter wrote:
>>
>>> I assume that the OpenVPN got disconnected for a few seconds, and
>>> came back again.
>>>
>>> My question is: assuming I have enough wal segments on Master side,
>>> does the Slave get synchronized automatically after the connection
>>> is reestablished, or I'll need to restart Slave PostgreSQL to put it
>>> in sync again?
>>>
>>> If I restart Slave PostgreSQL, I get:
>>
>> Yes, it automatically catches up when the connection is working
>> again. You should not have to restart the slave.
> Thanks! Would be a nice improvement if when replication is
> restablished, then a log message occur.
>
> Regards,
>
> Edson.
>>
>> John DeSoi, Ph.D.
>>
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2011-12-03 07:23:30 | Re: Postgresql + corrupted disk = data loss. (Need help for database recover) |
Previous Message | gouse shaik | 2011-12-03 02:37:33 |