Re: pgsql: Add reusable routine for making arrays unique.

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Thomas Munro <tmunro(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Add reusable routine for making arrays unique.
Date: 2020-01-06 01:46:48
Message-ID: CAH2-Wzno_rYiz=L0zaBrxJaPFHj-fpajCnriwv83M4awDvj6Ug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sun, Jan 5, 2020 at 5:39 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Looking at the stats, it's clear that it took a lot of code from other
> files, so it seems disingenuous to claim that it doesn't have even a
> single line that isn't copyrighted by UCB regents.

I took that claim at face value. Perhaps it was just an oversight.
But if it really wasn't, then it's not just "portions" of the
copyright that go to the PGDG.

> I think the easiest is to state that all files, even new files are
> Portions (c) each of these entities, period. Trying to distinguish code
> that's not even a single line derived from UCB Regents seems really
> labor-intensive.

That seems like a reasonable policy to me, outside of third-party code
that gets vendored into the tree. I am also in favor of being
conservative about this.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2020-01-06 02:06:50 Re: pgsql: Add reusable routine for making arrays unique.
Previous Message Peter Geoghegan 2020-01-06 01:43:26 pgsql: Remove redundant incomplete split assertion.