From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | Mitchell Bösecke *EXTERN* <mitchell(dot)bosecke(at)forcorp(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Safe to delete archived log files generated by ongoing transaction? |
Date: | 2014-07-23 13:54:13 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17D1F537@ntex2010i.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Mitchell Bösecke wrote:
> I have a long running transaction (> 24 hours) running on a development machine and so far it's
> generated more than 50 gigs of log files which are being archived to another disk. That disk is
> starting to run low and I'm wondering if deleting these logs will affect the ongoing transaction at
> all? I.e. does a commit or a rollback require access to the original transaction logs?
The database server will not be affected if you delete the WAL archives.
> The postgresql instance is version 9.2, the base backup was generated using the pg_basebackup utility
> with the "--xlog" parameter so if necessary I should also be able to recover without the use of those
> log files, correct?
However, you will lose the ability to do point-in-time recovery.
So if you have such a backup, you can restore it, but you will lose the
ability to replay any of the changes that happened since.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | John Scalia | 2014-07-23 17:16:49 | Can't get a standby built |
Previous Message | Mitchell Bösecke | 2014-07-23 13:36:51 | Safe to delete archived log files generated by ongoing transaction? |