Re: Remove Deprecated Exclusive Backup Mode
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: Robert Haas <robertmhaas@gmail.com>, David Steele <david@pgmasters.net>, Andres Freund <andres@anarazel.de>, Adrien NAYRAT <adrien.nayrat@anayrat.info>, Fujii Masao <masao.fujii@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-02-26T04:41:28Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Remove exclusive backup mode
- 39969e2a1e4d 15.0 landed
Greetings Mark, * Mark Kirkwood (mark.kirkwood@catalyst.net.nz) wrote: > ISTM that the onus should be on the patch submitter to provide additions to > pg_basebackup that make it as painless as possible for those people *not* > using pgBackRest to continue making backups. Breaking this is just not > right. Submitting patches that mean that people *must* use pgBackRest is > also not right IMHO. I'm sorry that there's some confusion here- to be clear, no one is required to use pgBackRest. pg_basebackup works quite well and wouldn't be impacted by the changes proposed no this thread. The arguments against removing the exclusive backup feature don't have anything to do with pg_basebackup. Thanks! Stephen