From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Marti Raudsepp <marti(at)juffo(dot)org> |
Cc: | Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Patch pg_is_in_backup() |
Date: | 2012-02-02 11:44:01 |
Message-ID: | CAFj8pRCW6EnNJGBqMciUX+AZWqtRZOtFHXKj8VsJKdZsXM1oig@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2012/2/2 Marti Raudsepp <marti(at)juffo(dot)org>:
> On Mon, Jan 30, 2012 at 20:33, Gilles Darold <gilles(dot)darold(at)dalibo(dot)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.
+1
Pavel
>
> Regards,
> Marti
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-02-02 13:45:44 | Re: spgist text_ops and LIKE |
Previous Message | hubert depesz lubaczewski | 2012-02-02 11:24:00 | Re: pg_dump -s dumps data?! |