Re: pg_standby replication problem - Mailing list pgsql-general

From Khangelani Gama
Subject Re: pg_standby replication problem
Date
Msg-id ce3ab4298e3cc6f2751653d6f50f0342@mail.gmail.com
Whole thread Raw
In response to pg_standby replication problem  (Khangelani Gama <kgama@argility.com>)
Responses Re: pg_standby replication problem
Re: pg_standby replication problem
List pgsql-general

Please please help

 

From: Khangelani Gama [mailto:kgama@argility.com]
Sent: Monday, June 09, 2014 1:42 PM
To: pgsql-general@postgresql.org
Subject: pg_standby replication problem

 

 

Please help me with this, my secondary server shows a replication problem. It stopped at the file called 0000000500004BAF000000AFthen from here primary server kept on sending walfiles, until the walfiles used up the disc space in the data directory. How do I fix this problem. It’s postgres 9.1.2.

Postgres log file Postgres-2014-06-08_000000.log file has the following details :

 2014-06-08 00:15:54 SAST LOG:  restored log file "0000000500004BAF000000AF" from archive

Trigger file:         /tmp/recovery.pgsql.trigger.5432

Waiting for WAL file: 0000000500004BAF000000B0

WAL file path:        /pgsql2/walfiles/0000000500004BAF000000B0

Restoring to:         pg_xlog/RECOVERYXLOG

Sleep interval:       2 seconds

Max wait interval:    0 forever

Command for restore:  cp "/pgsql2/walfiles/0000000500004BAF000000B0" "pg_xlog/RECOVERYXLOG"

Keep archive history: 0000000500004BAE000000F7 and later

WAL file not present yet. Checking for trigger file...

WAL file not present yet. Checking for trigger file...

WAL file not present yet. Checking for trigger file...

WAL file not present yet. Checking for trigger file...

WAL file not present yet. Checking for trigger file...

 

 

 

 

 


CONFIDENTIALITY NOTICE
The contents of and attachments to this e-mail are intended for the addressee only, and may contain the confidential
information of Argility (Proprietary) Limited and/or its subsidiaries. Any review, use or dissemination thereof by anyone
other than the intended addressee is prohibited.If you are not the intended addressee please notify the writer immediately
and destroy the e-mail. Argility (Proprietary) Limited and its subsidiaries distance themselves from and accept no liability
for unauthorised use of their e-mail facilities or e-mails sent other than strictly for business purposes.

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL 9.2.4 + CentOS 6.5 64 bit - segfault error in initdb
Next
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL 9.2.4 + CentOS 6.5 64 bit - segfault error in initdb