From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: katsuaki.fukushima@gmail.com
Subject: BUG #16854: initdb fails on ReFS and FAT32 file systems
Date: Fri, 05 Feb 2021 04:55:39 +0000
Message-ID: <16854-905604506e23d5c0@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16854
Logged by: Katsuaki Fukushima
Email address: katsuaki.fukushima@gmail.com
PostgreSQL version: 13.1
Operating system: Windows 10 Enterprise and Windows Server 2019
Description:
In Microsoft Windows, initdb fails for ReFS and FAT32 file systems.
PostgreSQL 12.x worked fine.
The WAL allocated in the temporary is renamed to the canonical name with the
durable_rename_excl function in src/backend/storage/file/fd.c.
This function hardlinks to the canonical name and unlinks the temporary.
Since ReFS does not support hard linking, the CreateHardLinkA function in
src/port/link.c will fail and the OS will return error code 50.
I replaced CreateHardLinka(dst, src, NULL) with MoveFileA(src, dst), and it
works for now.
I haven't investigated the effect on others.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, katsuaki.fukushima@gmail.com
Subject: Re: BUG #16854: initdb fails on ReFS and FAT32 file systems
In-Reply-To: <16854-905604506e23d5c0@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox