Re: WSL (windows subsystem on linux) users will need to turn fsyncoff as of 11.2 - Mailing list pgsql-general

From James Sewell
Subject Re: WSL (windows subsystem on linux) users will need to turn fsyncoff as of 11.2
Date
Msg-id CAANVwEtX9Z1X2H9r3hbDGmCwGM81tCAXdCkAi_j2HeGuV+zDqg@mail.gmail.com
Whole thread Raw
In response to Re: WSL (windows subsystem on linux) users will need to turn fsyncoff as of 11.2  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: WSL (windows subsystem on linux) users will need to turn fsyncoff as of 11.2  (Andres Freund <andres@anarazel.de>)
List pgsql-general
Right, the first step would be for a WSL user to figure out what's
wrong with builds on the WSL and show us how to fix it; I heard
through the grapevine that if you try it, initdb doesn't work (it must
be something pretty subtle in the configure phase or something like
that, since the Ubuntu .deb apparently works, except for the issue
reported in this thread). 

That's correct - initdb doesn't work when you've built on WSL as *somehow* HAVE_FDATASYNC is set to 1 by configure - but it ends up not being included by #ifdef blocks. This causes the following PANIC

PANIC:  unrecognized wal_sync_method: 1

Which happens because wal_sync is set to 1, but in src/backend/access/transam/xlog.c that block in the switch is inside the #ifdef so never gets checked,

--
James


The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.

pgsql-general by date:

Previous
From: Jitendra Loyal
Date:
Subject: Re: BEFORE ... Statement-level trigger
Next
From: Andres Freund
Date:
Subject: Re: WSL (windows subsystem on linux) users will need to turn fsyncoff as of 11.2