Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id C7B279FB378 for ; Tue, 13 Feb 2007 18:26:37 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 85142-06 for ; Tue, 13 Feb 2007 18:26:34 -0400 (AST) X-Greylist: delayed 00:20:49.363387 by SQLgrey-1.7.4 Received: from kea.bulletinwireless.net (nat.bulletinwireless.net [60.234.49.2]) by postgresql.org (Postfix) with ESMTP id 86FC59FB34D for ; Tue, 13 Feb 2007 18:26:34 -0400 (AST) Received: from [192.168.1.13] (shaggy.dmz.jungledrum.co.nz [192.168.3.254]) (Authenticated sender: zach) by kea.bulletinwireless.net (Postfix) with ESMTP id 5492D17CB6; Wed, 14 Feb 2007 11:05:40 +1300 (NZDT) Message-ID: <45D23635.1070601@bulletinwireless.com> Date: Wed, 14 Feb 2007 11:05:41 +1300 From: Zach Bagnall User-Agent: Thunderbird 1.5.0.9 (X11/20070117) MIME-Version: 1.0 To: pgsql-admin@postgresql.org CC: "Joshua D. Drake" , Peter Eisentraut , radhika@88thstreet.com Subject: Re: Postgresql Upgrade 7.4 to 8.2 References: <21058.63.118.86.10.1169649336.squirrel@www.88thstreet.com> <200701241703.28901.peter_e@gmx.net> <45B79349.7050108@commandprompt.com> In-Reply-To: <45B79349.7050108@commandprompt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50 X-Spam-Level: X-Archive-Number: 200702/184 X-Sequence-Number: 24649 On 01/25/07 06:11, Joshua D. Drake wrote: > Peter Eisentraut wrote: >> Radhika Sambamurti wrote: >>> 1. How is the backup and recovery using WAL logging in 8.2 >> >> It's great! > > Less filling! > > Seriously though, the PITR recovery mechanism is quite mature and usable. I would say it is a good start - and progress is clearly being made. But it wont be "usable" for most serious applications until we have per-database transaction logging and backup recovery. Having to run a new instance (or obliterate the main instance) for recovery simply isn't practical.