On 2020-Jan-06, Michael Paquier wrote:
> On Sun, Jan 05, 2020 at 05:46:48PM -0800, Peter Geoghegan wrote:
> > On Sun, Jan 5, 2020 at 5:39 PM Alvaro Herrera
> > wrote:
> >> I think the easiest is to state that all files, even new files are
> >> Portions (c) each of these entities, period. Tryin
On Sun, Jan 05, 2020 at 05:46:48PM -0800, Peter Geoghegan wrote:
> On Sun, Jan 5, 2020 at 5:39 PM Alvaro Herrera
> 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 cop
On Sun, Jan 5, 2020 at 5:39 PM Alvaro Herrera 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 wa
On 2020-Jan-04, Peter Geoghegan wrote:
> On Wed, Nov 6, 2019 at 8:03 PM Thomas Munro wrote:
> > Add reusable routine for making arrays unique.
>
> I noticed that some of the copyright notices added by this commit look
> like this:
>
> + * Portions Copyright (c) 2019, PostgreSQL Global Developme
On Wed, Nov 6, 2019 at 8:03 PM Thomas Munro wrote:
> Add reusable routine for making arrays unique.
I noticed that some of the copyright notices added by this commit look
like this:
+ * Portions Copyright (c) 2019, PostgreSQL Global Development Group
Shouldn't this simply read "Copyright (c) 20
Add reusable routine for making arrays unique.
Introduce qunique() and qunique_arg(), which can be used after qsort()
and qsort_arg() respectively to remove duplicate values. Use it where
appropriate.
Author: Thomas Munro
Reviewed-by: Tom Lane (in an earlier version)
Discussion:
https://postgr.
