| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, 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-30 21:15:28 |
| Message-ID: | 20200130211528.GA3748@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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 <alvherre(at)2ndquadrant(dot)com> wrote:
> >> 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.
>
> That's also a no-brainer. So +1 to that. If we were to make that
> more formal, could we add something in the docs in [1]? An idea could
> be a new section dedicated to it.
That seems too extreme for me. I'm happy to leave it as a gentlemen's
agreement.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2020-01-30 22:34:01 | pgsql: Handle lack of DSM slots in parallel btree build. |
| Previous Message | Alvaro Herrera | 2020-01-30 16:55:32 | pgsql: Clean up newlines following left parentheses |