Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id B99C79FB565 for ; Fri, 19 Oct 2007 03:40:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 51459-04 for ; Fri, 19 Oct 2007 03:40:07 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by postgresql.org (Postfix) with ESMTP id EB98E9FC10F for ; Fri, 19 Oct 2007 03:40:08 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id u77so880792pyb for ; Thu, 18 Oct 2007 23:40:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=DD+7AjPR2WuwTVohwncMOHP0i2EVd3VlMVEPk6ApNE8=; b=aMjIzCHzmkx5aicAK8YyJfhMDqyeWQjBx9VxwtSgamJ4sTOQXH/3y6ksYPaozgYGIFATRgdIDGaajrdVxG/NTeMApfBm635zwnx3ug0xclM2ZpieYjB1vVthXOniaxtuQuHTHddF4OL4onezctCb+ZAQYVMLt45+1UGqGH/IELw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=UhikSVJFbH5mo1D+cQEJ0O7un4xKybcq7GcPc37I9NBvJEECcoerSHab1caT6JRo3fGy4LTnp3dICNwN7zB9nrQl2fsqyFHvYwKl6CkPBAbIPHGT577s9q5tFV9w7LyiNE+X7Vh+f6yai8Ummxsu+eVcDlOdvABcMnRDx+tOdFo= Received: by 10.65.156.2 with SMTP id i2mr2728519qbo.1192776007606; Thu, 18 Oct 2007 23:40:07 -0700 (PDT) Received: by 10.65.243.12 with HTTP; Thu, 18 Oct 2007 23:40:07 -0700 (PDT) Message-ID: <2ca799770710182340y9877687i8e82cd6847f37c5a@mail.gmail.com> Date: Fri, 19 Oct 2007 09:40:07 +0300 From: "Mikko Partio" To: pgsql-admin@postgresql.org Subject: Continuous archiving and wal generation MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5100_11612130.1192776007601" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/187 X-Sequence-Number: 27101 ------=_Part_5100_11612130.1192776007601 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello list I have a question concerning the continuous archiving process. The manual says: To make use of the backup, you will need to keep around all the WAL segment files generated during and after the file system backup. To aid you in doing this, the pg_stop_backup function 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 to have to make use of the backup. For example, if the starting WAL file is 0000000100001234000055CD the backup history file will be named something like 0000000100001234000055CD.007C9330.backup. My question is: if I have a large database which takes some time to backup with tar, and during the interval between pg_start_backup() and pg_stop_backup() more than one wal file gets generated, do I have to store in addition to the base backup all wal files generated during the backup interval or just the one specified by the .backup file? I'm trying to figure out the minimum required to restore from a backup, and my common sense says that I should archive all the wal files produced during the backup since they contain information of the data file changes made during the backup. Regards M ------=_Part_5100_11612130.1192776007601 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello list

I have a question concerning the continuous archiving process. The manual says:

To make use of the backup, you will need to keep around all the WAL segment files generated during and after the file system backup. To aid you in doing this, the pg_stop_backup function 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 to have to make use of the backup. For example, if the starting WAL file is 0000000100001234000055CD the backup history file will be named something like 0000000100001234000055CD.007C9330.backup .

My question is: if I have a large database which takes some time to backup with tar, and during the interval between pg_start_backup() and pg_stop_backup() more than one wal file gets generated, do I have to store in addition to the base backup all wal files generated during the backup interval or just the one specified by the .backup file?

I'm trying to figure out the minimum required to restore from a backup, and my common sense says that I should archive all the wal files produced during the backup since they contain information of the data file changes made during the backup.

Regards

M
------=_Part_5100_11612130.1192776007601--