Re: Remove Deprecated Exclusive Backup Mode

David Steele <david@pgmasters.net>

From: David Steele <david@pgmasters.net>

To: Michael Paquier <michael@paquier.xyz>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Magnus Hagander <magnus@hagander.net>

Date: 2018-12-20T10:29:48Z

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/20/18 1:35 AM, Michael Paquier wrote:
> On Wed, Dec 19, 2018 at 06:38:00PM +0200, David Steele wrote:
>> I'll push this to the first post-PG12 CF when one appears.  Can we just go
>> ahead and create a 2019-07 CF now?  I know we generally discuss this at
>> PGCon, but we can always rename it, right?
> 
> The schedule gets decided at the developer meeting, still the commit
> fests created can have their name and start/end dates modified as needed
> So, I think that it is not an issue to add one ahead now.  And here you
> go:
> https://commitfest.postgresql.org/23/
> 
> This request was going to pop out at some point anyway in the follow-up
> months.

Thanks, Michael.  Getting this error, not sure what it means:

Cannot move patch to the same commitfest, and multiple future 
commitfests exist!

-- 
-David
david@pgmasters.net