Ah, got it. Thanks!
On Dec 23, 2006, at 5:59 PM, Tom Lane wrote:
Ben <[EMAIL PROTECTED]> writes:
But, this page confuses me when it talks about pg_start_backup and
pg_stop_backup. What do these functions do? It seems like they do
nothing more than let me know which wal files were in use over t
Ben <[EMAIL PROTECTED]> writes:
> But, this page confuses me when it talks about pg_start_backup and
> pg_stop_backup. What do these functions do? It seems like they do
> nothing more than let me know which wal files were in use over the
> duration of the backup, which is certainly useful. Bu
Thanks for the pointer. This does look like what I want, because in
retrospect I don't know how I would know which wal logs I would start
to replay after a given pg_dumpall to bring myself up to the present
after a recovery.
But, this page confuses me when it talks about pg_start_backup and
I think you might want to do incremental backups so a better approach to
that as you mentioned too will be WAL files. For details you can refer to
--> http://www.postgresql.org/docs/current/static/continuous-archiving.html
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 12
Hi everybody,
I'm trying to find a good solution to making backups to tape, where I
want to define "good" as:
- easy to use, like pg_dumpall, BUT
- not in a single file, so I don't backup my entire database cluster
with every differential backup
As I understand my backup program (Bacula)
