Re: Using pg_start_backup() and pg_stop_backup()

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Using pg_start_backup() and pg_stop_backup()
Date: 2013-07-17 01:49:52
Message-ID: 51E5F840.3040800@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2013-07-17 01:59:03 Re: Using pg_start_backup() and pg_stop_backup()
Previous Message David B Harris 2013-07-17 01:21:09 Re: Using pg_start_backup() and pg_stop_backup()