Re: branches_of_interest.txt

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: branches_of_interest.txt
Date: 2018-07-02 12:05:22
Message-ID: CA+TgmoY3_mJaXbvTZ1y68MxgvVcT7GA3_ePvGKjncc1zRmRPVA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 2, 2018 at 4:39 AM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-07-02 12:14:59 Re: ERROR: cannot start subtransactions during a parallel operation
Previous Message Masahiko Sawada 2018-07-02 12:01:15 Re: Avoid extra Sort nodes between WindowAggs when sorting can be reused