On Thu, Aug 23, 2007 at 06:58:36PM -0400, Bill Moran wrote:
Decibel! [EMAIL PROTECTED] wrote:
On Aug 19, 2007, at 7:23 AM, Bill Moran wrote:
Assumptions:
a. After pg_stop_backup(), Pg immediately recycles log files and
hence wal
logs can be copied to backup. This is a clean
On Aug 19, 2007, at 7:23 AM, Bill Moran wrote:
Assumptions:
a. After pg_stop_backup(), Pg immediately recycles log files and
hence wal
logs can be copied to backup. This is a clean start.
I don't believe so. ARAIK, all pg_stop_backup() does is remove the
marker that pg_start_backup() put
Decibel! [EMAIL PROTECTED] wrote:
On Aug 19, 2007, at 7:23 AM, Bill Moran wrote:
Assumptions:
a. After pg_stop_backup(), Pg immediately recycles log files and
hence wal
logs can be copied to backup. This is a clean start.
I don't believe so. ARAIK, all pg_stop_backup() does is
I'm guessing you're in a hurry or in a pinch that you need to repost
after one day on a weekend. I was waiting to let someone more
knowledgeable answer, but I've had some experience with this, so
I'll answer to the best of my ability.
I apologize. I wasn't sure if my first email ended up
Joey K. wrote:
After reading the docs, PITR is still fuzzy. Our ideas for backup are (do
not worry about the syntax),
Maybe consider using LVM snapshots in conjunction with rdiff-backup as
an option well. Simple to setup, simple to manage, no downtime, very
space efficient.
--
Best regards,
Joey K. [EMAIL PROTECTED] wrote:
Greetings,
I'm guessing you're in a hurry or in a pinch that you need to repost
after one day on a weekend. I was waiting to let someone more
knowledgeable answer, but I've had some experience with this, so
I'll answer to the best of my ability.
We have
Greetings,
We have several web applications with Pg 8.2.x running on isolated servers
(~25). The database size on each machines (du -h pgdata) is ~2 GB. We have
been using nightly filesystem backup (stop pg, tar backup to ftp, start pg)
and it worked well.
We would like to move to PITR backups
