Re: pg_standby replication problem

Поиск
Список
Период
Сортировка
От Khangelani Gama
Тема Re: pg_standby replication problem
Дата
Msg-id 9d8c8f249498b1ad59953a21f8779559@mail.gmail.com
обсуждение исходный текст
Ответ на pg_standby replication problem  (Khangelani Gama <kgama@argility.com>)
Список pgsql-general
Дерево обсуждения

The big question we can’t answer is that when the replication was at this point (Command for restore:  cp "/pgsql2/walfiles/0000000500004BAF000000B0" "pg_xlog/RECOVERYXLOG"

) , it then started to say WAL file not present yet. We can’t find this 0000000500004BAF000000B0 file any where .

 

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...

 

 

-rw------- 1 postgres postgres 16M Jun  7 21:42 0000000500004BAE000000F7

 

 

 

 

 

 

 

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

 

 

 

Filesystem            Size  Used Avail Use% Mounted on

/dev/sda3              57G   15G   39G  28% /

/dev/mapper/vg0-pgsql2

                      5.4T  5.3T     0 100% /pgsql2

/dev/sda1              99M   12M   83M  13% /boot

tmpfs                  30G     0   30G   0% /dev/shm

 

 

Disc space Breakdown:

 

 

4.0K    ./backup

12K     ./copy

4.9T    ./data

204K    ./test

16K     ./lost+found

361G    ./walfiles

5.3T    .

 

 

 

 

 

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 0000000500004BAF000000AF …then 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 по дате отправления:

Предыдущее
От: Khangelani Gama
Дата:
Сообщение: Re: pg_standby replication problem
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: PostgreSQL 9.2.4 + CentOS 6.5 64 bit - segfault error in initdb