The big feature I am being pestered for is :
- hot backup that (subsequent) logs can be applied to during recovery
The patch in its current form provides this - which is excellent.
However, some "easyness" enhancements could be in order :
- automatically archiving logs after a hot backup to <somewhere>
- some sort of ability to detect if the archived log sequence is
"broken" anywhere after the lastest hot backup.
I would like to see PITR as straightforward as possible to setup.
Backups that are actually unrestorable - because the Dba didn't
understand the product's convoluted "design" - are still way too
pgsql-hackers-pitr by date
|Next:||From: Tom Lane||Date: 2004-02-13 04:35:03|
|Subject: Re: [HACKERS] PITR Dead horse? |
|Previous:||From: Cott Lang||Date: 2004-02-13 01:25:35|
|Subject: Re: Review of last summer's PITR patch|