Re: pg_rewind in contrib - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_rewind in contrib
Date
Msg-id CAB7nPqS6rdGA9Ajm4DkVH8ecqBx4UZLXcVtt=cmr1QzYgxRXuQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_rewind in contrib  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Wed, Jan 7, 2015 at 5:39 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> Also, since you have been maintaining this tool for a while, what is the
> effort for maintaining it from version to version?
From my own experience, the main source of maintenance across major
versions is the modification of the WAL record format to be able to
track the blocks that need to be copied from the newly promoted master
to the node rewound. That has been an ongoing effort on REL9_4_STABLE
and REL9_3_STABLE since this tool has been created when both versions
were in development to keep the tool compatible all the time. This
problem does not exist anymore on master thanks to the new WAL format
able to track easily the blocks modified, limiting the maintenance
necessary to actual bugs.
-- 
Michael



pgsql-hackers by date:

Previous
From: Kouhei Kaigai
Date:
Subject: Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)
Next
From: Jim Nasby
Date:
Subject: Re: Updating copyright notices to 2015 for PGDG