| From: | "Gilberto Castillo" <gilberto(dot)castillo(at)etecsa(dot)cu> |
|---|---|
| To: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | "'Gustav Karlsson *EXTERN*'" <gustav(dot)karlsson(at)bekk(dot)no>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Deleting old WAL-files |
| Date: | 2015-05-19 13:29:34 |
| Message-ID: | 59237.192.168.207.54.1432042174.squirrel@webmail.etecsa.cu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> Gustav Karlsson wrote:
>> I am looking for a good method of determining what WAL-segments can be
>> deleted from our backup-
>> archive.
>>
>> We are using Postgresql 9.3 and do nightly basebackups along with
>> archiving of WAL-segments.
>>
>> We would like to prevent our backup-archive from growing forever, and
>> thus delete basebackups and WAL-
>> segments older than say 1 year.
>>
>> Is there a good way of finding the oldest WAL-segment needed for a given
>> basebackup? (If not, what is
>> the typical method for deleting old WAL-segments?)
>
> The backup contains a file "backup_label" which contains a line like
>
> START WAL LOCATION: 0/83000028 (file 000000010000000000000083)
>
> That is the oldest file needed for recovery.
>
> But a simple solution would be to keep WAL archives for one day more than
> your oldest
> base backup, that way you can never miss a WAL archive that you need.
See you:
http://www.postgresql.org/docs/current/static/pgarchivecleanup.html
Saludos,
Gilberto Castillo
ETECSA, La Habana, Cuba
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/plain | 179 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Graeme B. Bell | 2015-05-19 14:26:30 | Performances issues with SSD volume ? |
| Previous Message | Matheus de Oliveira | 2015-05-19 12:53:10 | Re: Create Index CONCURRENTLY Hangs Indefinitely. |