| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | johnlumby(at)hotmail(dot)com |
| Cc: | PostgreSQL mailing lists <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 07:23:58 |
| Message-ID: | CAB7nPqSaj3vHsW9361hacr=Uh0Os3Fq8bNUPd-Edb6pb15Jv_A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Apr 25, 2016 at 4:25 AM, <johnlumby(at)hotmail(dot)com> wrote:
> However, what I believe *is* needed is to update the target control file
> with the new timeline and other information from the source.
No, this is incorrect. There is no need to update the control file of
a node that has not been rewound, and pg_rewind should not mess up
with that if there is no divergence point between the target and the
source nodes or it would update the minimum recovery point of a node
without real need to do so. It should be able to join back the cluster
depending on its initial shutdown state (when you shut down systemA).
What are the logs of your system A telling you regarding its startup
state?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | srkunze | 2016-04-25 11:23:33 | BUG #14110: information_schema.constraint_column_usage not working as expected |
| Previous Message | johnlumby | 2016-04-24 19:25:49 | BUG #14109: pg_rewind fails to update target control file in one scenario |