Re: Remove Deprecated Exclusive Backup Mode

David Steele <david@pgmasters.net>

From: David Steele <david@pgmasters.net>

To: Magnus Hagander <magnus@hagander.net>, Robert Haas <robertmhaas@gmail.com>

Cc: Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2018-12-27T17:03:31Z

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

On 12/27/18 6:53 PM, Magnus Hagander wrote:
> On Fri, Dec 21, 2018 at 5:43 PM Robert Haas <robertmhaas@gmail.com 
> 
>     I think the old CommitFest application let you set the CommitFest via
>     the Edit screen also, so you could pick a specific CommitFest to
>     target.  But that doesn't seem to exist in Magnus's version.
> 
> The basics is, there is not supposed to be more than one Future 
> commitfest, in order to keep the workflow as simple as possible. When 
> there is, all sorts of bad things happen. What we really should have at 
> that point is a blocker so you can't *create* more than one of them, but 
> right now it naively assumes nobody does...

Which is ironic since I specifically requested that one be created.

-- 
-David
david@pgmasters.net