>
>
> > I mean, could random bytes appear as a valid record (very unlikely, but
> > possible)?
>
> Yes, that could be possible if some memory or disk is broken. That's
> why, while it is important to take backups, it is more important to
> make sure that they are able to restore correctly before
On Tue, Jan 10, 2017 at 10:35 PM, Tom DalPozzo wrote:
> I redid the tests following your suggestion to issue a checkpoint manually.
> IT WORKS!
> Just a question: when the standby server starts, I see the log error
> messages (ex.: "invalid record length...") when WAL end
>
> Could you give more details? What does pg_rewind tell you at each
>> phase? Is that on Postgres 9.5 or 9.6? I use pg_rewind quite
>> extensively on 9.5 but I have no problems of this time with multiple
>> timeline jumps when juggling between two nodes. Another thing that is
>> coming to my
2017-01-06 13:09 GMT+01:00 Michael Paquier :
> On Fri, Jan 6, 2017 at 1:01 AM, Tom DalPozzo wrote:
> > Hi,
> > there is something happening in my replication that is not clear to me. I
> > think I'm missing something.
> > I've two server, red and
On Fri, Jan 6, 2017 at 1:01 AM, Tom DalPozzo wrote:
> Hi,
> there is something happening in my replication that is not clear to me. I
> think I'm missing something.
> I've two server, red and blue.
> red is primary blue is standby, async repl.
> Now:
> 1 cleanly stop red
> 2
Hi,
there is something happening in my replication that is not clear to me. I
think I'm missing something.
I've two server, red and blue.
red is primary blue is standby, async repl.
Now:
1 cleanly stop red
2 promote blue
3 insert tuples in blue
4 from red site, pg_rewind from blue to red dir.
5