Re: Named restore points - Mailing list pgsql-hackers

From Thom Brown
Subject Re: Named restore points
Date
Msg-id AANLkTi=ZsjfsPJO-Y-fTVSMSfyHf91OocC8h=kx5SY2T@mail.gmail.com
Whole thread Raw
In response to Re: Named restore points  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Named restore points  (Euler Taveira de Oliveira <euler@timbira.com>)
List pgsql-hackers
On 8 February 2011 19:53, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Tue, 2011-02-08 at 14:07 -0300, Euler Taveira de Oliveira wrote:
>
>> Because named restore point is a noop xlog record; besides, transaction and
>> time involves xlog records that contain data.
>
> Committed. Thanks for the patch and the review.
>
> I changed the patch to require wal_level > minimal, rather than
> archive_mode = on.

This could do with a bit more documentation about usage.  Below the
Backup Control Functions table
(http://developer.postgresql.org/pgdocs/postgres/functions-admin.html#FUNCTIONS-ADMIN-BACKUP-TABLE),
each function has a paragraph detailing what it does.

Also, I notice you can easily write over a label.  The case I'm
thinking of is someone in psql creating a named restore point, then
later on, they go in again, accidentally cursor up and select the
previous statement and create it again.  Would this mean that the
previous label is lost, or would it be the case that any subsequent
duplicate labels would have no effect unless the WAL files with the
original label in were consumed?  In either case, a note in the docs
about this would be useful.

And I don't see these label creations getting logged either.  Could we
output that to the log because at least then users can grep the
directory for labels, and, in most cases, the time they occurred?

-- 
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Extensions support for pg_dump, patch v27
Next
From: Dimitri Fontaine
Date:
Subject: Re: Extensions versus pg_upgrade