Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yug4v-0006AR-DH for pgsql-admin@arkaria.postgresql.org; Tue, 19 May 2015 11:52:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Yug4u-0003Zq-U6 for pgsql-admin@arkaria.postgresql.org; Tue, 19 May 2015 11:52:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Yug4t-0003YL-Ma for pgsql-admin@postgresql.org; Tue, 19 May 2015 11:52:55 +0000 Received: from mout.web.de ([212.227.15.3]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.84) (envelope-from ) id 1Yug4l-0006g6-NW for pgsql-admin@postgresql.org; Tue, 19 May 2015 11:52:55 +0000 Received: from vm-mailsrv.lan.net ([87.155.102.86]) by smtp.web.de (mrweb004) with ESMTPSA (Nemesis) id 0Lj88M-1ZSMzr1uiE-00dBpN for ; Tue, 19 May 2015 13:52:45 +0200 Received: from localhost (localhost [127.0.0.1]) by vm-mailsrv.lan.net (Postfix) with ESMTP id 50335F12E for ; Tue, 19 May 2015 13:52:43 +0200 (CEST) X-Spam-Flag: NO X-Spam-Score: -2.898 X-Spam-Level: X-Spam-Status: No, score=-2.898 tagged_above=-99.9 required=6.31 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, FREEMAIL_FROM=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from vm-mailsrv.lan.net ([127.0.0.1]) by localhost (vm-mailsrv.lan.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6rcGc0j9U4Tx for ; Tue, 19 May 2015 13:52:39 +0200 (CEST) Received: from neslonek.homeunix.org (vm-webapp-ext.dmz-lan.net [192.168.0.100]) by vm-mailsrv.lan.net (Postfix) with ESMTP id B834EF12B for ; Tue, 19 May 2015 13:52:39 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 19 May 2015 13:52:39 +0200 From: Jan Lentfer To: Subject: Re: Deleting old WAL-files In-Reply-To: <5FB35597-0F52-4832-973D-908F5B01BE9B@bekk.no> References: <5FB35597-0F52-4832-973D-908F5B01BE9B@bekk.no> Message-ID: <12819ff9dc22928bdb69e5de36b62338@imap.lan.net> X-Sender: Jan.Lentfer@web.de User-Agent: Roundcube Webmail/0.7.2 X-Provags-ID: V03:K0:Szz9SmaMx4gD3alpmly8+OcWVnt8vlqd0ZAfXCgsh3fp61oniUz ZudVlbDjoavqycr6r7Mipnvah13E3ZWgfc/cUtyoyHnzu1vJzKTPV/E80SXVrsEz30V7DHC QzfG3VtnaRFUSqqRHmrcBDemu7JdfU2al+kTPWYuxX2uQfVXoj9/RmDKzBqPL6Zw7QEbTEA CTCYzQzKuFIEW9SqdIMAg== X-UI-Out-Filterresults: notjunk:1; X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org 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