X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 76A40D1E91C for ; Mon, 22 Mar 2004 16:34:08 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 78618-10 for ; Mon, 22 Mar 2004 12:34:16 -0400 (AST) Received: from fep01-mail.bloor.is.net.cable.rogers.com (fep01-mail.bloor.is.net.cable.rogers.com [66.185.86.71]) by svr1.postgresql.org (Postfix) with ESMTP id EB3EED1E150 for ; Mon, 22 Mar 2004 12:34:05 -0400 (AST) Received: from phlogiston.dydns.org ([65.49.121.67]) by fep01-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20040322163340.MBMY138614.fep01-mail.bloor.is.net.cable.rogers.com@phlogiston.dydns.org> for ; Mon, 22 Mar 2004 11:33:40 -0500 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id 7C7EF3C0E; Mon, 22 Mar 2004 11:34:15 -0500 (EST) Date: Mon, 22 Mar 2004 11:34:15 -0500 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: Restoring DB From A Log? Message-ID: <20040322163415.GC11738@phlogiston.dyndns.org> Mail-Followup-To: pgsql-admin@postgresql.org References: <_8GcnZrZwrXI3sHdRWPC-g@speakeasy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <_8GcnZrZwrXI3sHdRWPC-g@speakeasy.net> User-Agent: Mutt/1.5.5.1+cvs20040105i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep01-mail.bloor.is.net.cable.rogers.com from [65.49.121.67] using ID at Mon, 22 Mar 2004 11:33:40 -0500 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/284 X-Sequence-Number: 12853 On Sat, Mar 20, 2004 at 08:12:02AM -0500, Al Cohen wrote: > In our particular situation, being down for two hours or so is OK. > What's really bad is losing data. > > The PostgreSQL replication solutions that we're seeing are very clever, > but seem to require significant effort to set up and keep going. Since > we don't care if a slave DB is ready to kick over at a moment's notice, > I'm wondering if there is some way to generate data, in real time, that > would allow an offline rebuild in the event of catastrophe. We could > copy this data across the 'net as it's available, so we could be OK even > if the place burned down. > Your closest current bet is one of the (admittedly possibly painful to use) async replication systems available. Note that _no_ async system, log shipping, whatever can guarantee zero data loss: if you lose the active master in a catastrophic explosion which consumes all your disk, there is the possibility that there will be records which were committed on that master but which were not committed anywhere else. This is even true of PITR approaches which stream the WAL to some system in another city: you're only as up to date as the last packet sent, and if a bomb goes off in your cage in your data centre, you're going to lose something no matter what. You might like to follow the Slony project, which has as one of its design goals much easier administration than erserver. You may also want to watch the PITR project, which appears to be aiming to get into 7.5. A -- Andrew Sullivan | ajs@crankycanuck.ca