Re: pg_rewind, a tool for resynchronizing an old master after failover - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_rewind, a tool for resynchronizing an old master after failover
Date
Msg-id 20130528200411.GI23164@momjian.us
Whole thread Raw
In response to Re: pg_rewind, a tool for resynchronizing an old master after failover  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List 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@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: pg_rewind, a tool for resynchronizing an old master after failover
Next
From: Szymon Guz
Date:
Subject: [PATCH] Fix conversion for Decimal arguments in plpython functions