| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Remove Deprecated Exclusive Backup Mode |
| Date: | 2018-12-27 17:03:31 |
| Message-ID: | 7600048f-1042-3cbd-2215-62bb09fec55f@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/27/18 6:53 PM, Magnus Hagander wrote:
> On Fri, Dec 21, 2018 at 5:43 PM Robert Haas <robertmhaas(at)gmail(dot)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(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-12-27 17:12:39 | Re: reducing the footprint of ScanKeyword (was Re: Large writable variables) |
| Previous Message | Andrew Dunstan | 2018-12-27 16:58:30 | Re: GIN predicate locking slows down valgrind isolationtests tremendously |