Re: Beta1 announcement: alpha1 draft
От | Stephen Frost |
---|---|
Тема | Re: Beta1 announcement: alpha1 draft |
Дата | |
Msg-id | 20160429111422.GQ10850@tamriel.snowman.net обсуждение исходный текст |
Ответ на | Re: Beta1 announcement: alpha1 draft (Josh berkus <josh@agliodbs.com>) |
Ответы |
Re: Beta1 announcement: alpha1 draft
|
Список | pgsql-advocacy |
* Josh berkus (josh@agliodbs.com) wrote: > On 04/27/2016 01:50 PM, Stephen Frost wrote: > > * Joshua D. Drake (jd@commandprompt.com) wrote: > >> On 04/27/2016 09:40 AM, Josh berkus wrote: > >> > >>> If it weren't for length, I'd be all for having a list of projects which > >>> are having a release to get ready for 9.6; we've done that several times > >>> before, and that's useful for testing too. "pgAdmin has been adjusted > >>> to support X in the new release, please test". I don't know that we > >>> have anything like that, though, do we? > >> > >> The only thing would be PgLogical but I don't think it warrants exclusivity. > > > > Not entirely sure I'm following along correctly, but if we're talking > > about tools being updated for 9.6, it seems likley that all of the > > backup tools which use pg_start/stop_backup will be updated for the new > > API. > > 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. Thanks! Stephen
Вложения
В списке pgsql-advocacy по дате отправления: