PostgreSQL 9.0 and asynchronous replication through VPN - Mailing list pgsql-general

From Edson Richter
Subject PostgreSQL 9.0 and asynchronous replication through VPN
Date
Msg-id 4ED5FF4F.90808@simkorp.com.br
Whole thread Raw
Responses Re: PostgreSQL 9.0 and asynchronous replication through VPN  (John DeSoi <desoi@pgedit.com>)
List pgsql-general
Dear friends,

I have an somewhat unstable link between two different locations with OpenVPN established and working.

Now, I've configured PostgreSQL 9.0.5 for asynchronous replication. This morning I got the following message on Slave PostgreSQL log:

------------------------------------------------------------------------------------------------------------------------------
2011-11-30 07:52:23 BRST % - FATAL:  could not connect to the primary server: could not connect to server: Connection timed out
        Is the server running on host "10.68.73.5" and accepting
        TCP/IP connections on port 5432?
   
2011-11-30 07:55:33 BRST % - FATAL:  could not connect to the primary server: could not connect to server: Connection timed out
        Is the server running on host "10.68.73.5" and accepting
        TCP/IP connections on port 5432?
-------------------------------------------------------------------------------------------------------------------------------

Detailed network configuration: PostgreSQL [Master = 10.68.73.5, Slave = 10.68.73.1]; OpenVPN [Server = 10.68.73.1; Client=10.68.73.5; both static IP]

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:

------------------------------------------------------------------------------------------------------------------------------------------------------
2011-11-30 08:01:09 BRST % - LOG:  received fast shutdown request
2011-11-30 08:01:09 BRST % - FATAL:  terminating walreceiver process due to administrator command
2011-11-30 08:01:09 BRST % - LOG:  shutting down
2011-11-30 08:01:09 BRST % - LOG:  database system is shut down
2011-11-30 08:01:18 BRST % - LOG:  database system was shut down in recovery at 2011-11-30 08:01:09 BRST
2011-11-30 08:01:18 BRST % - LOG:  entering standby mode
2011-11-30 08:01:18 BRST % - LOG:  redo starts at A/4000020
2011-11-30 08:01:18 BRST % - LOG:  record with zero length at A/40000B0
------------------------------------------------------------------------------------------------------------------------------------------------------

Thanks for your help,
--

Edson Carlos Ericksson Richter
SimKorp Informática Ltda
Fone:(51) 3366-7964
Celular:(51)9318-9766/(51) 8585-0796
Embedded Image

Attachment

pgsql-general by date:

Previous
From: BK
Date:
Subject: Strange problem with turning WAL archiving on
Next
From: "Albe Laurenz"
Date:
Subject: Re: odbc_fdw