| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: requested timeline ... does not contain minimum recovery point ... |
| Date: | 2018-07-13 18:06:50 |
| Message-ID: | 01A4F489-4C30-400E-B7AA-D29B0D20BCA7@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Jul 12, 2018, at 19:54, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Do you see a "checkpoint complete: wrote ..." message
> before the rewind started?
Checking, but I suspect that's exactly the problem.
This raises a question: Would it make sense for pg_rewind to either force a checkpoint or have a --checkpoint option along the lines of pg_basebackup? This scenario (pg_rewind being run very quickly after secondary promotion) is not uncommon when there's scripting around the switch-over process.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Seiler | 2018-07-13 18:20:15 | Re: [PATCH] Include application_name in "connection authorized" log message |
| Previous Message | Heikki Linnakangas | 2018-07-13 17:34:36 | Re: [HACKERS] PATCH: Keep one postmaster monitoring pipe per process |