Re: Using pg_start_backup() and pg_stop_backup() - Mailing list pgsql-general

From John R Pierce
Subject Re: Using pg_start_backup() and pg_stop_backup()
Date
Msg-id 51E5F840.3040800@hogranch.com
Whole thread Raw
In response to Re: Using pg_start_backup() and pg_stop_backup()  (David B Harris <dbharris@eelf.ddts.net>)
Responses Re: Using pg_start_backup() and pg_stop_backup()
List pgsql-general
On 7/16/2013 6:21 PM, David B Harris wrote:
> Actually though (if any PostgreSQL developers are paying attention), it
> might be useful to have a new WAL segment-managing behaviour. With the
> advent of the replication functionality (which is amazing stuff, thanks
> so much), I'd expect fewer and fewer installations to use WAL archiving.
> If WAL archiving is disabled, it might make sense for pg_start_backup()
> to postpone the deletion of WAL segments until pg_stop_backup().

WAL archiving has another completely different use case, which is PITR,
Point In Time Recovery.



--
john r pierce                                      37N 122W
somewhere on the middle of the left coast



pgsql-general by date:

Previous
From: David B Harris
Date:
Subject: Re: Using pg_start_backup() and pg_stop_backup()
Next
From: Michael Paquier
Date:
Subject: Re: Using pg_start_backup() and pg_stop_backup()