Re: mklink of pg_standby - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: mklink of pg_standby
Date
Msg-id 20080121130002.GI10643@svr2.hagander.net
Whole thread Raw
In response to mklink of pg_standby  ("Hiroshi Saito" <z-saito@guitar.ocn.ne.jp>)
List pgsql-hackers
On Mon, Jan 21, 2008 at 03:36:29PM +0900, Hiroshi Saito wrote:
> Hi Simon, and Dave,Magnus.
> 
> About pg_standby, a link option cause a problem in windows(XP and 2k,2k3).
> It is because the call of mklink is needed. Then, they are the new programs 
> of VISTA and 2008. It is CreateSymbolicLink of API of kernel32.lib is 
> equipped with mklink.
> http://msdn2.microsoft.com/en-us/library/aa363866.aspx
> 
> Therefore, I considered whether it should correspond by the 'Junction' or 
> the 'Hard Link' this way and that. However, The addition thought that it 
> was not desirable by the reason of the process of evolution functional 
> pg_standby. A copy function is no problem. However, I think that it is 
> necessary to write it to a document in order to avoid a user's confusion. 
> probably, has that no source code corrects.
> 
> to Dave,and Magnus.
> You can do more honest suggestion.:-)

Junctions only work for directories, not for files.

In theory, you should be able to use mklink to create a hardlink on
previous versions of Windows, but I'm not sure if it'll work. But we want
symlinks here, not hardlinks, and they are simply not supported on earlier
versions of Windows.

It is alerady documented that it doesn't work on Windows prior to Vista. I
think this is fine. What we could add is a specific version check to
pg_standby to have it emit a "not supported on this windows version" error
if it's not supported. But I think that's overkill - it will still fail,
and it's well documented that it's not *supposed* to work.

//Magnus


pgsql-hackers by date:

Previous
From: ohp@pyrenet.fr
Date:
Subject: Re: sun to buy mysql
Next
From: Magnus Hagander
Date:
Subject: Re: mklink of pg_standby