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

From Dave Page
Subject Re: pg_rewind, a tool for resynchronizing an old master after failover
Date
Msg-id CA+OCxow9pgVc-2wUAZJTkHBR7qB1mAD1=prAdd5+8z=wRfBK7w@mail.gmail.com
Whole thread Raw
In response to Re: pg_rewind, a tool for resynchronizing an old master after failover  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On Wed, Jun 5, 2013 at 6:10 PM, Josh Berkus <josh@agliodbs.com> wrote:
>
>> I'm not a lawyer and I make no judgement on how solid a practice this
>>> is but that's VMware doesn't seem to be doing anything special here.
>>> They can retain copyright ownership of their contributions as long as
>>> they're happy releasing it under the Postgres copyright. Ideally they
>>> wold also be happy with a copyright notice that includes all of the
>>> PGDG just to reduce the maintenance headache.
>
> Many other projects also take this approach: Linux Kernel, Drizzle, etc.
>  There's some legal advantages, as well as disadvantages, in having the
> copyright rest with the original contributors.  Mostly, it prevents
> relicensing of the whole project.

No it doesn't - it just makes it a pain in the arse (I know, I've done it).

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Possible bug in cascaded standby
Next
From: Fujii Masao
Date:
Subject: Re: Redesigning checkpoint_segments