Thank You, I will have a look.
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Tuesday, June 10, 2014 3:45 PM
To: Khangelani Gama; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_standby replication problem
On 06/09/2014 10:02 PM, Khangelani Gama
On 06/09/2014 10:02 PM, Khangelani Gama wrote:
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Tuesday, June 10, 2014 1:42 AM
To: Khangelani Gama; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_standby replication problem
On 06/09/2014 11:15 AM
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Tuesday, June 10, 2014 1:42 AM
To: Khangelani Gama; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_standby replication problem
On 06/09/2014 11:15 AM, Khangelani Gama wrote:
> This is the stan
On 06/09/2014 11:15 AM, Khangelani Gama wrote:
This is the standby replication setting with archive_command sending the
WALs from master to standby.
What are the conf settings on the standby server?
--
Adrian Klaver
adrian.kla...@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-g
On Monday, June 09, 2014 08:05:41 PM Khangelani Gama wrote:
> Hi All
>
> I would like to re-post the problem we have. The secondary server ran out
> the disc space due the replication problem (Connection Time out).
The secondary server would not (could not) run out of drive space due to a
proble
This is the standby replication setting with archive_command sending the
WALs from master to standby.
-Original Message-
From: Khangelani Gama [mailto:kg...@argility.com]
Sent: Monday, June 09, 2014 8:06 PM
To: pgsql-general@postgresql.org
Subject: pg_standby replication problem
Hi All
Hi All
I would like to re-post the problem we have. The secondary server ran out
the disc space due the replication problem (Connection Time out).Since there
was a Connection time out Problem in the primary server, how can I make disc
space in the secondary server for the replication to continue f
-Original Message-
From: Khangelani Gama [mailto:kg...@argility.com]
Sent: Monday, June 09, 2014 5:26 PM
To: 'Alan Hodgson'; 'pgsql-general@postgresql.org'
Subject: RE: [GENERAL] pg_standby replication problem
I just saw got this from the primary server (/tmp/ru
I just saw got this from the primary server (/tmp/run_replication.sh.out),
secondary server's IP 10.58.101.10.
replication started: Sun Jun 8 00:05:26 SAST 2014 source:
pg_xlog/00054BAF00AF, dest: 00054BAF00AF
replication finished: Sun Jun 8 00:05:33 SAST 2014
replicati
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Alan Hodgson
Sent: Monday, June 09, 2014 4:51 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_standby replication problem
On Monday, June 09, 2014 04:28:53 PM
On Monday, June 09, 2014 04:28:53 PM Khangelani Gama wrote:
> Please help me with this, my secondary server shows a replication problem.
> It stopped at the file called *00054BAF00AF …*then from here
> primary server kept on sending walfiles, until the walfiles used up the
> disc space
On 06/09/2014 07:28 AM, Khangelani Gama wrote:
Please please help
Before anyone can help you will need to provide more information on what
your archiving, replication setup is. To begin:
1)Are you doing both archiving and streaming replication?
2) What are the settings in the configuration
Please please help
*From:* Khangelani Gama [mailto:kg...@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
The big question we can’t answer is that when the replication was at this
point (*Command for restore: cp
"/pgsql2/walfiles/00054BAF00B0" "pg_xlog/RECOVERYXLOG"*
) , it then started to say WAL file not present yet. We can’t find
this *00054BAF00B0
*file any where* . *
*
FilesystemSize 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 spac
Please help me with this, my secondary server shows a replication problem.
It stopped at the file called *00054BAF00AF** …*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.
16 matches
Mail list logo