| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Curt Sampson <cjs(at)cynic(dot)net> |
| 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:05:34 |
| Message-ID: | 14644.1045296334@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Curt Sampson | 2003-02-15 08:23:49 | Re: Incremental backup |
| Previous Message | Curt Sampson | 2003-02-15 07:46:53 | Re: Incremental backup |