X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 131E18B9F1E for ; Fri, 4 Feb 2005 08:42:56 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 87859-06 for ; Fri, 4 Feb 2005 08:42:51 +0000 (GMT) Received: from mail.tanto.de (mail.tanto.de [213.61.178.43]) by svr1.postgresql.org (Postfix) with ESMTP id 8F1898B9E69 for ; Fri, 4 Feb 2005 08:42:51 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by mail.tanto.de (Postfix) with ESMTP id 6E28523BF1; Fri, 4 Feb 2005 09:42:52 +0100 (CET) Received: from mail.tanto.de ([127.0.0.1]) by localhost (mail.tanto.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18024-10; Fri, 4 Feb 2005 09:42:52 +0100 (CET) Received: from tucholsky.office.tanto.de (tucholsky.office.tanto.de [10.0.0.35]) by mail.tanto.de (Postfix) with ESMTP id 439A323BF0; Fri, 4 Feb 2005 09:42:52 +0100 (CET) Received: from tucholsky.office.tanto.de (morus@localhost [127.0.0.1]) by tucholsky.office.tanto.de (8.12.3/8.12.3/Debian-7.1) with ESMTP id j148h172015310; Fri, 4 Feb 2005 09:43:01 +0100 Received: (from morus@localhost) by tucholsky.office.tanto.de (8.12.3/8.12.3/Debian-7.1) id j148h1Gu015306; Fri, 4 Feb 2005 09:43:01 +0100 From: Morus Walter MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16899.13717.792766.260214@tanto-xipolis.de> Date: Fri, 4 Feb 2005 09:43:01 +0100 To: pgsql-admin@postgresql.org Cc: "Simon Riggs" Subject: Re: PITR WAL backups In-Reply-To: References: <42012233.40700@everytruckjob.com> X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid X-Virus-Scanned: by amavisd-new at mail.tanto.de Q&A postmaster@tanto.de X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200502/29 X-Sequence-Number: 16197 Simon Riggs writes: > >Mark Reidenbach wrote > > >The problem I'm having is that you need to > > backup this wal > > file before it's been archived to have a backup which is > > consistent > > Not sure I agree. Can you explain some more? > > Is it that you have a very low transaction rate and log files take a > long time to fill? > Independently from the transaction rate it's not clear to me, at which point (that is after saving which WAL) an online backup will be safe to be usable. I start the backup, save the files, end the backup. Ok. Now there are transactions during the backup. They are written to WALs. Some of these WALs are archived but the last transaction might be stored in WALs that are not archived yet, when the backup ends. So when can I be sure, to have all transactions that occured during the backup in archived WALs? Do I just have to wait that there is one further WAL archived after the backup? If that's the case, then online backups at low transaction rates might take some time. I guess one can live with that. If you keep the previous backup and the WALs so far, you can still recover from that, while waiting for the current backup to become safe. But the documentation it didn't make clear to me, at which point I can rely on the backup. Morus