Re: PITR Dead horse?

From: Christopher Browne <cbbrowne(at)acm(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PITR Dead horse?
Date: 2004-02-08 05:05:52
Message-ID: m3r7x6f9e7.fsf@wolfe.cbbrowne.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

A long time ago, in a galaxy far, far away, pgman(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) wrote:
> Austin Gonyou wrote:
>> As previously stated by Bruce I believe, the mindshare department needs
>> some work. For this, the PITR is a necessity, but also when comparing
>> features with other DBs that people and businesses are currently
>> familiar with.
>
> PITR is required to recover all data after total hardware failure. It
> isn't just a mindshare issue.

One of the valuable "use cases" of PITR is in replication, and
correspondingly, one of the valuable "use cases" of replication is in
doing major version upgrades.

As a result, a _really valuable thing_ would be for the "PITR reader"
process to be able to read data from "more elderly" versions of
PostgreSQL.

That may not prove practical, but the more flexible it is, the more
useful it certainly is...
--
"cbbrowne","@","cbbrowne.com"
http://www.ntlug.org/~cbbrowne/wp.html
Space Corps Directive #997: Work done by an officer's doppleganger in
a parallel universe cannot be claimed as overtime. -- Red Dwarf

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nigel J. Andrews 2004-02-08 10:52:07 Re: RFC: Security documentation
Previous Message Tom Lane 2004-02-08 04:59:25 Re: Advice regarding configuration parameters