Re: Incremental backup

From: Curt Sampson <cjs(at)cynic(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Incremental backup
Date: 2003-02-15 08:26:03
Message-ID: Pine.NEB.4.51.0302151724050.361@angelic-vtfw.cvpn.cynic.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 15 Feb 2003, Tom Lane wrote:

> Curt Sampson <cjs(at)cynic(dot)net> writes:
> > ... But there's really no need for all fifty of those,
> > if you don't mind not being able to restore to any time before the
> > current time.
>
> Which, of course, is exactly the point of PITR designs.
>
> When you know that your assistant trainee DBA deleted most of your
> database with a mistyped command last Tuesday evening around 8pm,
> it is cold comfort to know that your database has faithfully preserved
> his committed changes. You want to get back to where you were Tuesday
> afternoon, or preferably Tuesday evening 7:59pm. This is what PITR
> setups can do for you.
>
> If you don't feel you need PITR capability, fine ... but don't tell
> the people who want it that they have no need for it.

Hey, I never said you *have* to do this compression!

I envisioned it as an option. I'd like, for example, to be able to aim a
program that the last eight weeks worth of log files and say, "compress
the first seven weeks of this, but leave the last week fully intact."
Then I can save some space (quite a lot, if my updates have certain
characteristics), and yet still get back to Tuesday evening at 7:59 p.m.

cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Curt Sampson 2003-02-15 08:29:21 Re: [HACKERS] WAL replay logic (was Re: Mount options for
Previous Message Curt Sampson 2003-02-15 08:23:49 Re: Incremental backup