>> > > > OK, I have applied the following patch that uses Cygwin native 
>> > > > symlink() instead of the Win32 junctions.  The reason 
>for this is 
>> > > > that Cygwin symlinks work on Win95/98/ME where 
>junction points do 
>> > > > not
>> > > 
>> > > Is this really a Win95/98/ME vs NT distinction or a FAT32 
>> > vs NTFS distinction?
>> > > In which case does an NT machine that happens to be using a 
>> > FAT32 file 
>> > > system have the same problem?
>> > 
>> > I believe it is OS, not file system.
>> 
>> No, it's file system.
>> Junctions will not work on NT OS:es with FAT32.
>> Directory junctions require NTFSv5, which is only available 
>on Windows
>> 2000 and newer.
>
>My point was that junctions don't exist on Win98 no matter what file
>system you use.  I don't think the API even exists on those OS's, never
>mind what file system you have.

The API exists - it's just a call to DeviceIOControl(). That one exists
on all win32 platforms. It will return a "not supported" error value,
but the API is there. (Unlike some other APIs where the program won't
even start because the entrypoint is not present in the system DLLs)

The only reason they are not in 9x is that 9x does not support NTFS. The
function is implemented only in the filesystem, not in the OS itself.


//Magnus

Wed, 13 Oct 2004 21:11:54 +0200
"Magnus Hagander" <mha@sollentuna.net>
Re: open item: tablespace handing in pg_dump/pg_restore