From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: contrecord is requested |
Date: | 2017-09-11 22:32:30 |
Message-ID: | CAB7nPqSsMFYPS5NwnpjuBWot6aBN_iN-BQuifatF2r5QkLr2ig@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 12, 2017 at 5:27 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> So we have a db we're trying to rewind and get synced to the master.
> pg_rewind says it doesn't need rewinding, and when we try to bring it
> up, it gets this error:
>
> "contrecord is requested by 2E7/40000028"
>
> And fails to get back up.
The consistency recovery point defined by pg_rewind was not reached then.
> Is this a known issue?
Never heard of this one.
> Possible bug in the continuation record code?
That looks like a possibility. This complains is about the fact that
the XLOG page header cannot be found where it should. You may want to
check your WAL segments.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Yogesh Sharma | 2017-09-12 01:02:16 | Perl script is killed by SIGPIPE |
Previous Message | Jeff Janes | 2017-09-11 21:32:33 | Re: pg_ident mapping Kerberos Usernames |