From: Jan Lentfer <Jan.Lentfer@web.de>
To: pgsql-admin@postgresql.org
Subject: Re: Deleting old WAL-files
Date: Tue, 19 May 2015 13:52:39 +0200
Message-ID: <12819ff9dc22928bdb69e5de36b62338@imap.lan.net> (raw)
In-Reply-To: <5FB35597-0F52-4832-973D-908F5B01BE9B@bekk.no>
References: <5FB35597-0F52-4832-973D-908F5B01BE9B@bekk.no>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Am 2015-05-19 13:43, schrieb Gustav Karlsson:
> 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?)
>
>
> (We are aware that Barman is offering this functionality, and might
> migrate to using it, but would still like to know the method used)
In short terms you need all the WAL segments created during and after
the base backup. It's also explained in the manual:
To make use of the backup, you will need to keep all the WAL segment
files generated during and after the file system backup. To aid you in
doing this, the base backup process creates a backup history file that
is immediately stored into the WAL archive area. This file is named
after the first WAL segment file that you need for the file system
backup. For example, if the starting WAL file is
0000000100001234000055CD the backup history file will be named something
like 0000000100001234000055CD.007C9330.backup
From:
http://www.postgresql.org/docs/9.4/interactive/continuous-archiving.html#BACKUP-BASE-BACKUP
hth
Jan
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: Jan.Lentfer@web.de
Subject: Re: Deleting old WAL-files
In-Reply-To: <12819ff9dc22928bdb69e5de36b62338@imap.lan.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox