PITR Recovery Question

From: "Gnanakumar" <gnanam(at)zoniac(dot)com>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: PITR Recovery Question
Date: 2010-06-03 13:37:07
Message-ID: 001201cb0321$df429d40$9dc7d7c0$@com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

Hi,

My production server is running PostgreSQL v8.2.3 on CentOS release 5.2
(Final).

I've setup PITR in my production server. For some reason, after setting up
PITR, we're not able to manage and maintain it. Because of this our WAL
archive drive become full (100% use) approximately after 1 month.

PITR SETUP DETAILS
We've 2 drives. Primary drive (pgsql/data/ directory resides) is 400 GB and
secondary drive (WAL archive) is 30 GB. All WAL archives are written to
secondary drive.

Base backup taken on: Aug03, 2009
WAL archive drive become full (100% use) on: Sep05, 2009

Because this WAL archive drive has become full, all WAL archive segments to
be archived are accumulated into pg_xlog/ directory itself. Eventually, 9
months (as of today from Sep05, 2009) of WAL archives are residing in
pg_xlog/ directory.

My question is, in case if I would like to perform recovery process as it is
in this situation, will this work out? That is, I'm seeing/finding out
whether recovery process would perform successfully anywhere between the
date range Aug03, 2009 (my base backup date) and as of today - Jun03, 2009.
Reason I'm asking this is still all my WAL archives are residing in pg_xlog/
directory.

Experts advice/idea/suggestion on this appreciated.

Regards,
Gnanam

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Kevin Grittner 2010-06-03 13:49:59 Re: PG_dump a large database fails
Previous Message Shoaib Mir 2010-06-03 09:15:46 Re: graceful reload

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-06-03 13:47:19 Re: "caught_up" status in walsender
Previous Message Bruce Momjian 2010-06-03 12:36:28 Re: Allow wal_keep_segments to keep all segments