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

From Simon Riggs
Subject Re: pg_rewind, a tool for resynchronizing an old master after failover
Date
Msg-id CA+U5nMJ=mnGF-52=MKm702LZ=qb+Hgg2vMndYxC7QW6zfVyirg@mail.gmail.com
Whole thread Raw
In response to pg_rewind, a tool for resynchronizing an old master after failover  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: pg_rewind, a tool for resynchronizing an old master after failover  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Re: pg_rewind, a tool for resynchronizing an old master after failover  (Greg Stark <stark@mit.edu>)
List pgsql-hackers
On 23 May 2013 12:10, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:

> Please take a look: https://github.com/vmware/pg_rewind

The COPYRIGHT file shows that VMware is claiming copyright on unstated
parts of the code for this. As such, its not a normal submission to
the PostgreSQL project, which involves placing copyright with the
PGDG.

As a result, while it sounds interesting, people should be aware of
that and I suggest we shouldn't discuss that code on this list, to
avoid any disputes should we decide to include a similar facility in
core Postgres in the future.

--Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_rewind, a tool for resynchronizing an old master after failover
Next
From: Simon Riggs
Date:
Subject: Re: Heap truncation without AccessExclusiveLock (9.4)