Re: Backup strategies

From: "Ivan Voras" <ivoras(at)freebsd(dot)org>
To: "Aidan Van Dyk" <aidan(at)highrise(dot)ca>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Backup strategies
Date: 2008-10-15 14:58:46
Message-ID: 9bbcef730810150758i4cc25431g41e4805c024615fd@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-performance

2008/10/15 Aidan Van Dyk <aidan(at)highrise(dot)ca>:
> * Ivan Voras <ivoras(at)freebsd(dot)org> [081015 10:05]:
>
>> So, pg_start_backup() freezes the data at the time it's called but still
>> data and xlog are changed, in a different way that's safe to backup? Why
>> not run with pg_start_backup() always enabled?
>
> I think your missing the whole point of "pg_start_backup()".
> pg_start_backup()" is *part* of a full PITR/backup run. i.e. you use it
> when you have an archive command working as well. It's *not* mean tto
> just allow you to do a filesystem copy inside a running data directory.

Possibly - that's why I'm sticking to this thread :) My context is
doing full filesystem-only copies/backups of the database (xlogs &
all) - is pg_start_backup() applicable?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robert Parker 2008-10-15 15:07:20 Re: Chart of Accounts
Previous Message Robert Treat 2008-10-15 14:50:01 Re: Column level triggers

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2008-10-15 15:51:53 Re: Backup strategies
Previous Message Peter Childs 2008-10-15 14:22:39 Re: Backup strategies