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 A44FB3A55DB for ; Mon, 24 Jan 2005 18:30:37 +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 82102-02 for ; Mon, 24 Jan 2005 18:30:25 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 206423A5574 for ; Mon, 24 Jan 2005 18:30:25 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j0OIUEDl023397; Mon, 24 Jan 2005 13:30:14 -0500 (EST) To: Scott Marlowe Cc: Pallav Kalva , pgsql-admin@postgresql.org Subject: Re: Postgres 8.0 Backups In-reply-to: <1106591222.16640.108.camel@state.g2switchworks.com> References: <41F52694.1090309@deg.cc> <1106586565.16640.90.camel@state.g2switchworks.com> <23143.1106589900@sss.pgh.pa.us> <1106591222.16640.108.camel@state.g2switchworks.com> Comments: In-reply-to Scott Marlowe message dated "Mon, 24 Jan 2005 12:27:02 -0600" Date: Mon, 24 Jan 2005 13:30:14 -0500 Message-ID: <23396.1106591414@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/253 X-Sequence-Number: 16112 Scott Marlowe writes: > On Mon, 2005-01-24 at 12:05, Tom Lane wrote: >> In the context of online backup operations, that advice isn't relevant >> anymore ... > Really, is this an 8.0 thing then, that I can make file system backups > and expect them to be coherent, or did I misunderhear what you meant and > this has to do with some other issue I'm not getting? No, it means that when doing PITR stuff you don't actually care that your base backup isn't consistent --- you expect WAL replay to fix it. See http://www.postgresql.org/docs/8.0/static/backup-online.html regards, tom lane