Tom Lane wrote:Bruce Momjian <[EMAIL PROTECTED]> writes:
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 and we have no way to know what system will be running the Cygwin binaries so the safest bet is to use the Cygwin versions. On Win32 native we only run on systems that support junctions.
I think this is probably a net loss, because what it will mean is that you cannot take a data directory built under a Cygwin postmaster and use it under a native postmaster, nor vice versa. Given the number of other ways in which we do not support pre-NT4 Windows systems, what is the benefit of allowing this one?
I assume Cygwin supports pre-NT4, and always has, and I see no reason to change that. Moving a data directory from Cygwin to native Win32 seems like a pretty rare usage to diable pre-NT4 on a platform the previously supported it.
ok, thanks. I'll communicate that.
It's a new feature, so people will not know what's going on, but they already asked about tablespace. And maybe someone wants to test that on his WinME laptop. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
