| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Josh berkus <josh(at)agliodbs(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Beta1 announcement: alpha1 draft |
| Date: | 2016-04-29 11:31:11 |
| Message-ID: | 20160429113111.GA9668@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Fri, Apr 29, 2016 at 07:14:22AM -0400, Stephen Frost wrote:
> > Damn, which means I need to test mine too. Where are these changes
> > documented?
>
> The changes are to pg_start/stop_backup and their updated definitions
> can be reviewed here:
>
> http://www.postgresql.org/docs/devel/static/functions-admin.html
>
> Note that it's technically backwards compatible, however, the existing
> exclusive backup approach is bad and may mean that the database doesn't
> automatically recover from a crash which happens while the backup is
> running. All backup tools should be updated to the new APIs to avoid
> that risk.
Is this risk new? Is it documented?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-04-29 11:32:10 | Re: Beta1 announcement: alpha1 draft |
| Previous Message | Stephen Frost | 2016-04-29 11:14:22 | Re: Beta1 announcement: alpha1 draft |