Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 7BF419FB8D0 for ; Tue, 13 Feb 2007 23:26:31 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 36222-09 for ; Tue, 13 Feb 2007 23:26:20 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from kea.bulletinwireless.net (nat.bulletinwireless.net [60.234.49.2]) by postgresql.org (Postfix) with ESMTP id B30799FA0C4 for ; Tue, 13 Feb 2007 23:26:26 -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 7603A17CB1; Wed, 14 Feb 2007 16:26:23 +1300 (NZDT) Message-ID: <45D28160.10309@bulletinwireless.com> Date: Wed, 14 Feb 2007 16:26:24 +1300 From: Zach Bagnall User-Agent: Thunderbird 1.5.0.9 (X11/20070117) MIME-Version: 1.0 To: "Joshua D. Drake" CC: Tom Lane , pgsql-admin@postgresql.org, 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> <45D23635.1070601@bulletinwireless.com> <1288.1171415555@sss.pgh.pa.us> <45D27B4F.4080005@commandprompt.com> In-Reply-To: <45D27B4F.4080005@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/189 X-Sequence-Number: 24654 On 02/14/07 16:00, Joshua D. Drake wrote: > Tom Lane wrote: >> Zach Bagnall writes: >>>> 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. > >> Don't hold your breath; that's not even on the agenda, much less >> something that's likely to appear soon. If you need separable recovery >> then run a different postmaster instance for each database. > > I would have to concur... if you need such a feature I would wonder why > you are running multiple databases within the same cluster at all. It's not exactly an exotic feature. Sybase has had it for as long as I can remember, as has Informix and DB2 (I'm told). The obvious reason for not running multiple instances is that postgresql will know how to use the available memory most efficiently. By splitting them up, each postmaster must be tuned and adjusted by a stupid human. Unless you meant using a new hardware server for each database..