Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l84UZ-0006pN-MM for pgsql-bugs@arkaria.postgresql.org; Fri, 05 Feb 2021 17:01:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l84UY-0004nB-6b for pgsql-bugs@arkaria.postgresql.org; Fri, 05 Feb 2021 17:01:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l84UY-0004n4-0X for pgsql-bugs@lists.postgresql.org; Fri, 05 Feb 2021 17:01:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l84UV-0000Gw-Vh for pgsql-bugs@lists.postgresql.org; Fri, 05 Feb 2021 17:01:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 115H1pU9111020; Fri, 5 Feb 2021 12:01:51 -0500 From: Tom Lane To: "Euler Taveira" cc: "Fujii Masao" , katsuaki.fukushima@gmail.com, pgsql-bugs@lists.postgresql.org, peter.eisentraut@2ndquadrant.com Subject: Re: BUG #16854: initdb fails on ReFS and FAT32 file systems In-reply-to: <0d8da46b-e35b-45cc-a674-2a0678aa8bc6@www.fastmail.com> References: <16854-905604506e23d5c0@postgresql.org> <59ad1f40-1bf2-a7e8-da22-7a279ea46efd@oss.nttdata.com> <106278.1612538775@sss.pgh.pa.us> <0d8da46b-e35b-45cc-a674-2a0678aa8bc6@www.fastmail.com> Comments: In-reply-to "Euler Taveira" message dated "Fri, 05 Feb 2021 13:28:29 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <111018.1612544511.1@sss.pgh.pa.us> Date: Fri, 05 Feb 2021 12:01:51 -0500 Message-ID: <111019.1612544511@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "Euler Taveira" writes: > On Fri, Feb 5, 2021, at 12:26 PM, Tom Lane wrote: >> ReFS is Microsoft's latest and greatest attempt at implementing a modern >> file system. I'd quantify the greatness pretty poorly if they left out >> hard links (I wonder what other essentials they didn't bother with) >> but maybe we have to support it. > It claims that the latest ReFS version (3.5) supports hard links [1]. Hmm, what [1] actually says about that is Version ReFS 3.5 formatted by Windows 10 Enterprise Insider Preview build 19536. Added hardlink support if fresh formatted volume. Can't use hardlink if upgraded from previous version so it's not exactly mainstream yet. But given that, I'm content to say "you can use ReFS if you have a version that supports hard links". We don't need to support work-in-progress filesystems. regards, tom lane