Skip site navigation (1) Skip section navigation (2)

Re: Postgresql Upgrade 7.4 to 8.2

From: Zach Bagnall <zach(dot)bagnall(at)bulletinwireless(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>, radhika(at)88thstreet(dot)com
Subject: Re: Postgresql Upgrade 7.4 to 8.2
Date: 2007-02-14 03:26:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On 02/14/07 16:00, Joshua D. Drake wrote:
> Tom Lane wrote:
>> Zach Bagnall <zach(dot)bagnall(at)bulletinwireless(dot)com> 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..

In response to

pgsql-admin by date

Next:From: Thomas PapkeDate: 2007-02-14 06:55:14
Subject: Re: Question to safe way for minor update
Previous:From: Joshua D. DrakeDate: 2007-02-14 03:00:31
Subject: Re: Postgresql Upgrade 7.4 to 8.2

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group