From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Dong Han <dhan(at)bluecatnetworks(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: WAL file accumulation on log shipping primary node |
Date: | 2011-12-13 01:15:36 |
Message-ID: | CADK3HHLQ7VMbh7siNLaQ4uMnH1Rcecett6t0qW0LjmVVE4mwUw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dong,
How are you copying the wal logs over to the secondary ? Since this is
loosely coupled I am wondering how the master would be effected by
load.
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On Tue, Dec 13, 2011 at 12:42 AM, Dong Han <dhan(at)bluecatnetworks(dot)com> wrote:
> Dear all,
>
>
>
> We have setup log shipping replication between primary node and 2 secondary
> nodes with Postgresql version 8.4.8. From the data replication points of
> view, everything is fine. However, under heavy data modification load - we
> have an extremely busy system, we saw WAL files keep accumulating on the
> primary node - new WAL files are copied to secondary node and restored
> properly, but the primary node keeps holding a large number of old WAL
> files. To the end, the WAL files fill up the database partition. Previously,
> we tested in a lighter load environment, we did not have similar problem.
>
>
>
> Please help to diagnosis the problem, and give me recommendations on how to
> fix this problem.
>
>
>
> Thank you very much.
>
>
>
> Dong Han
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scot Kreienkamp | 2011-12-13 03:22:29 | Re: initdb with lc-collate=C |
Previous Message | Dong Han | 2011-12-13 00:42:48 | Re: WAL file accumulation on log shipping primary node |