Re: BUG #14109: pg_rewind fails to update target control file in one scenario - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #14109: pg_rewind fails to update target control file in one scenario
Date
Msg-id CAB7nPqTVeSD_Poqe0YFcgttJtYAAkfZD_aKhrjZ6tO86eas7LQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14109: pg_rewind fails to update target control file in one scenario  (John Lumby <johnlumby@hotmail.com>)
Responses Re: BUG #14109: pg_rewind fails to update target control file in one scenario
List pgsql-bugs
On Tue, Apr 26, 2016 at 7:15 AM, John Lumby <johnlumby@hotmail.com> wrote:
> So,  assuming this is reliable (will work without requiring archiving)
> then my problem is solved.

Depending on the checkpoint frequency and the activity on your
systems, you may face problems with missing WAL segments at some point
because past WAL segments need to be recycled or removed by the server
to move on with its life. One way to take care of this class of
problems is to use wal_keep_segments. An even better one is called
replication slot. This solely depends on how your system is working,
so perhaps you will not need some extra configuration.
--
Michael

pgsql-bugs by date:

Previous
From: John Lumby
Date:
Subject: Re: BUG #14109: pg_rewind fails to update target control file in one scenario
Next
From: Benedikt Grundmann
Date:
Subject: Re: BUG #14111: After minor upgrade (9.2.6 -> 9.2.16): ERROR: failed to build any 2-way joins