Re: Patch pg_is_in_backup() - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Patch pg_is_in_backup()
Date
Msg-id CABUevExm4_a-Yw3pt=weppb5ckzAYZwK3e79m__sznQNjjDveg@mail.gmail.com
Whole thread Raw
In response to Re: Patch pg_is_in_backup()  (Marti Raudsepp <marti@juffo.org>)
Responses Re: Patch pg_is_in_backup()  (Euler Taveira de Oliveira <euler@timbira.com>)
List pgsql-hackers
On Thu, Feb 2, 2012 at 12:23, Marti Raudsepp <marti@juffo.org> wrote:
> On Mon, Jan 30, 2012 at 20:33, Gilles Darold <gilles.darold@dalibo.com> wrote:
>> After some time searching for a Pg system administration function like
>> pg_is_in_recovery(), let's say pg_is_in_backup(), I couldn't find one.
>> The minor patch attached here adds this administrative function that can
>> be used with others backup control functions. This is a very little
>> patch outside documentation because the function is only a wrapper to
>> the internal BackupInProgress() function, just like pg_is_in_recovery()
>> is calling RecoveryInProgress().
>
> I think it would be more useful to have a function that returns a
> timestamp when the backup started. That way, it's possible to write a
> generic monitoring script that alerts the sysadmin only when a backup
> has been running for too long, but is silent for well-behaved backups.

If there is more than one concurrent backup running, which one do you
return? The first one or the latest one? Or perhaps you need an
interface thta can return them all...

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Bernd Helmle
Date:
Subject: Re: Patch pg_is_in_backup()
Next
From: Tom Lane
Date:
Subject: Re: Patch: Allow SQL-language functions to reference parameters by parameter name