Re: Gather Merge

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Gather Merge
Date: 2016-11-04 19:42:47
Message-ID: CAEepm=2KSe-H-NBzYDqmZQt9-Q8KXPAaJrYONoLFTsO791xg4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Nov 5, 2016 at 2:42 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
>> On Fri, Nov 4, 2016 at 12:00 PM, Thomas Munro
>> <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
>>> Shouldn't this say just "(c) 2016, PostgreSQL Global Development
>>> Group"? Are we supposed to be blaming the University of California
>>> for new files?
>
>> If the new file contains a portion of code from this age, yes.
>
> My habit has been to include the whole old copyright if there's anything
> at all in the new file that could be considered to be copy-and-paste from
> an existing file. Frequently it's a gray area.

Thanks. I see that it's warranted in this case, as code is recycled
from MergeAppend.

> Legally, I doubt anyone cares much. Morally, I see it as paying due
> respect to those who came before us in this project.

+1

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Karl O. Pinc 2016-11-04 20:07:52 Re: Patch to implement pg_current_logfile() function
Previous Message Amit Kapila 2016-11-04 19:41:13 Re: Hash Indexes