Re: branches_of_interest.txt - Mailing list pgsql-hackers

From Robert Haas
Subject Re: branches_of_interest.txt
Date
Msg-id CA+TgmoY3_mJaXbvTZ1y68MxgvVcT7GA3_ePvGKjncc1zRmRPVA@mail.gmail.com
Whole thread Raw
In response to Re: branches_of_interest.txt  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Mon, Jul 2, 2018 at 4:39 AM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 01.07.18 17:41, Tom Lane wrote:
>> I can see the value of people other than you being able to change it,
>> but keeping it in the core repo seems like a kluge not a proper solution.
>> In particular, once it'd been around for awhile so that the master copy
>> had diverged from the back branches' copies, that would be pretty
>> confusing IMO.
>
> Yeah, I'd find this kind of weird.  The version control system contains
> the code, not the other way around.

+1.  But I like the idea of using something to which there is broader access.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Avoid extra Sort nodes between WindowAggs when sorting can be reused
Next
From: Robert Haas
Date:
Subject: Re: ERROR: cannot start subtransactions during a parallel operation