| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | John Lumby <johnlumby(at)hotmail(dot)com> |
| Cc: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, pgsql bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14109: pg_rewind fails to update target control file in one scenario |
| Date: | 2016-04-25 23:04:58 |
| Message-ID: | CAB7nPqTVeSD_Poqe0YFcgttJtYAAkfZD_aKhrjZ6tO86eas7LQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Apr 26, 2016 at 7:15 AM, John Lumby <johnlumby(at)hotmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benedikt Grundmann | 2016-04-26 06:53:45 | Re: BUG #14111: After minor upgrade (9.2.6 -> 9.2.16): ERROR: failed to build any 2-way joins |
| Previous Message | John Lumby | 2016-04-25 22:15:12 | Re: BUG #14109: pg_rewind fails to update target control file in one scenario |