On Sun, Oct 1, 2017 at 10:03 AM, Thomas Munro <thomas.mu...@enterprisedb.com> wrote: >> I tried few more times, and I've got it two times from four attempts on a >> fresh >> installation (when all instances were on the same machine). But anyway I'll >> try >> to investigate, maybe it has something to do with my environment. >> >> ... >> >> 2017-09-30 15:47:55.154 CEST [6030] LOG: invalid magic number 0000 in log >> segment 000000010000000000000020, offset 10092544 > > Hi Dmitry, > > Thanks for testing. Yeah, it looks like the patch may be corrupting > the WAL stream in some case that I didn't hit in my own testing > procedure. I will try to reproduce these failures.
Hi Dmitry, I managed to reproduce something like this on one of my home lab machines running a different OS. Not sure why yet and it doesn't happen on my primary development box which is how I hadn't noticed it. I will investigate and aim to get a fix posted in time for the Commitfest. I'm also hoping to corner Simon at PGDay Australia in a couple of weeks to discuss this proposal... -- Thomas Munro http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers