From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | Roberto Scattini <roberto(dot)scattini(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_xlog and standby |
Date: | 2008-01-24 01:07:28 |
Message-ID: | Pine.GSO.4.64.0801231954450.12679@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 23 Jan 2008, Roberto Scattini wrote:
> the problem that im having is that i have A LOT of
> archive files on pg_xlog dir, and thats because the archive_command
> keeps failing (the standby server had filled his disk with archives
> received but not proccesed), so now, i dont know how i can remove
> those files and start again...
Under normal operation the checkpoint process will look at the number of
already created archive files, keep around up to (2*checkpoint_segments+1)
of them for future use, and delete the rest of them. You never delete
them yourself, the server will take care of that automatically once it
gets to where it makes that decision. If you set checkpoint_segments to
some very high number they can end up taking many GB worth of storage,
increasing that parameter has at least two costs associated with it (the
other being a longer recovery time).
Managing old archive logs on the backup server is your problem and related
tools like pg_standby help deal with that. Managing them on the primary
server is that server's problem and you shouldn't touch them. You can
execute a manual CHECKPOINT at the psql prompt if you want to force this
reclaimation to happen (there has to have been some activity since the
last checkpoint for this to work which doesn't sound like a problem on
your server).
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2008-01-24 01:11:29 | Re: constraints in table |
Previous Message | Dominique Bessette - Halsema | 2008-01-24 00:09:10 | constraints in table |