Re: pg_rewind, a tool for resynchronizing an old master after failover

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pjw(at)rhyme(dot)com(dot)au
Subject: Re: pg_rewind, a tool for resynchronizing an old master after failover
Date: 2013-05-28 20:04:11
Message-ID: 20130528200411.GI23164@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 28, 2013 at 03:49:14PM -0400, Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > Oh, I see. Have we historically been OK with these as long as it is
> > clear it is the PG copyright? I know we had do some cleanups in the
> > past, but I don't remember the details, obviously.
>
> We've had request from companies because they wanted to distribute
> Postgres and lawyers weren't comfortable with copyright statements in
> assorted files. In those cases we've asked the people mentioned in such
> copyright statements, got approval to remove the offending copyright
> lines, and removed them.

OK, so it was different _licenses_ that was the problem. OK.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Szymon Guz 2013-05-28 20:41:22 [PATCH] Fix conversion for Decimal arguments in plpython functions
Previous Message Christophe Pettus 2013-05-28 19:53:46 Re: pg_rewind, a tool for resynchronizing an old master after failover