Re: BUG #15303: Postgres fail to start if pg_wal is symlink, and works when it's a junction point

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: qwadrillion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15303: Postgres fail to start if pg_wal is symlink, and works when it's a junction point
Date: 2018-07-28 04:01:49
Message-ID: 20180728040149.GA1682@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jul 27, 2018 at 08:37:55AM +0000, PG Bug reporting form wrote:
> Postgres fail to start if pg_wal is directory symbolic link:
> $ mklink /D pg_wal C:\***\jul_25\transaction_log\pg_wal

That's working as designed and that's not a bug. Postgres has many code
paths where symbolic link handling of any other *nix platform maps to
junction points for Windows.

There may be some room for supporting direct symbolic links, but is that
really worth it knowing that junction points (mklink /J) work as
expected?
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2018-07-28 17:21:11 Re: pg_restore: All GRANTs on table fail when any one role is missing
Previous Message Michael Paquier 2018-07-28 00:10:12 Re: BUG #15182: Canceling authentication due to timeout aka Denial of Service Attack