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 8C26E8B9E5E for ; Tue, 1 Feb 2005 13:25:23 +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 73199-07 for ; Tue, 1 Feb 2005 13:25:08 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by svr1.postgresql.org (Postfix) with ESMTP id 954938B9E47 for ; Tue, 1 Feb 2005 13:25:08 +0000 (GMT) Received: by wproxy.gmail.com with SMTP id 67so760680wri for ; Tue, 01 Feb 2005 05:25:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:cc:subject:date:organization:message-id:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:in-reply-to:x-mimeole:importance; b=T5ITlg+pGh7Bwoq20pmIFnBVbCya9uAMGTSHA2r+Cmshu4+zcYWS/BQaaWMVeULyMTlxAdAM9iikHrH7p/08HtgPQJoUMQEwpkWvMVL0mtbG6lu+QpMj2W9vjKSfI9uXoNivJq+Foplw8QEKVPV76VT0cOvGUOMJdxJfX/zXpPQ= Received: by 10.54.21.37 with SMTP id 37mr100924wru; Tue, 01 Feb 2005 05:25:08 -0800 (PST) Received: from sbew318anc22 ([200.184.93.96]) by smtp.gmail.com with ESMTP id 43sm335070wri.2005.02.01.05.25.07; Tue, 01 Feb 2005 05:25:08 -0800 (PST) From: "Bruno Almeida do Lago" To: "'Morus Walter'" Cc: Subject: Re: Online Backup and WAL archives Date: Tue, 1 Feb 2005 11:26:13 -0200 Organization: G&P Message-ID: <001001c50861$9cc84e30$e883f40a@br.gedasgrp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <16895.32035.914311.612690@tanto-xipolis.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.116 tagged_above=0 required=5 tests=AWL, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200502/6 X-Sequence-Number: 16174 You may need to recreate some indexes: "Operations on non-B-tree indexes (hash, R-tree, and GiST indexes) are = not presently WAL-logged, so replay will not update these index types. The recommended workaround is to manually REINDEX each such index after completing a recovery operation." Best Regards, Bruno Almeida do Lago =20 -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Morus Walter Sent: Tuesday, February 01, 2005 10:59 AM To: pgsql-admin@postgresql.org Subject: [ADMIN] Online Backup and WAL archives Hi, I'm currently considering to use postgresql 8.0 online backups. The documentation says=20 ' To make use of this backup, you will need to keep around all the=20 WAL segment files generated at or after the starting time of the backup. = ' Now I'm wondering how much of these WAL segment files do I really need in order to recover the databases to a consistent state. Let's say I cannot write the WAL segments to tape dynamically when they are archived. Then a complete disk failure would mean, that I loose WAL=20 segments also. Therefore I would like to save a minimum number of WAL segments at or after the online backup that allows recovery. Is that possible? How would I decide how much of the WAL I need? Of course I could recover to the state of database at about the time of = the=20 backup only, but it would be a consistent state at least. Or should I use the previous online backup plus all WAL segements up to the current backup? I expect the online backup to faster on recovery than an SQL dump, since the latter would imply recreation of indexes during recovery. Therefore I would prefer to use online backups. Morus ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings