Re: Patch pg_is_in_backup()
От | Fujii Masao |
---|---|
Тема | Re: Patch pg_is_in_backup() |
Дата | |
Msg-id | CAHGQGwFuqazEaT+YCDUoZe-HwQ-txcq=djgisayyWnHhWn+1aQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Patch pg_is_in_backup() (Bernd Helmle <mailings@oopsware.de>) |
Ответы |
Re: Patch pg_is_in_backup()
|
Список | pgsql-hackers |
On Fri, Feb 3, 2012 at 6:10 PM, Bernd Helmle <mailings@oopsware.de> wrote: > > > --On 3. Februar 2012 13:21:11 +0900 Fujii Masao <masao.fujii@gmail.com> > wrote: > >> It seems to be more user-friendly to introduce a view like pg_stat_backup >> rather than the function returning an array. > > > I like this idea. A use case i saw for monitoring backup_label's in the > past, was mainly to discover a forgotten exclusive pg_stop_backup() (e.g. > due to broken backup scripts). If the view would be able to distinguish > both, exclusive and non-exclusive backups, this would be great. Agreed. Monitoring an exclusive backup is very helpful. But I wonder why we want to monitor non-exclusive backup. Is there any use case? If we want to monitor non-exclusive backup, why not pg_dump backup? If there is no use case, it seems sufficient to implement the function which reports the information only about exclusive backup. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: