>>>>The only downside to removal is that folks without symlinks 
>(I believe
>>>>Win32 only) will loose that functionality with nothing to 
>replace it.
>>>>However, I think the clarity of removing it is worth it.  
>Also, I think
>>>>someone had a special way to do symlinks on Win32 and we should look
>>>>into that.
>>>>
>>>>
>>>>      
>>>>
>>>Windows 2000 and later support mount points - you can attach a new
>>>partition as C:\pgsql\data\xlog instead of D:\. That might 
>be enough for
>>>most users. IIRC there was a tool to create arbitrary links, 
>but it was
>>>removed just before W2K final.
>>>
>>>    
>>>
>>If you run NTFS, it's still possible to use arbitrary links. 
>In the Windows
>>world, they are called junctions. Microsoft does not provide 
>a junction tool
>>for some reason (perhaps because it's limited to NTFS). A 
>good tool, free
>>and with source, can be found here
>>http://www.sysinternals.com/ntw2k/source/misc.shtml#junction 
>I use this tool
>>myself. Works like a charm.
>>
>>  
>>
>
>We've looked at it before. Apart from anything else I don't think its 
>license is compatible with PostgreSQL's.

Well, people can still use it. We just can't distribute it... We can
always link to it.
But unless there is a GUI tool (actually, unless it shows up in the
*default* GUI tool), expect there to be questions. An 


>Also, IIRC NTFS junctions also have some severe limitations.

The main being they can't do files, and there are few tools for them.
Also, most win32 admins are *NOT* experienced with them. Sure, they are
used for the NETLOGON directory, but how many admins know that...

//Magnus

Mon, 17 May 2004 21:18:26 +0200
"Magnus Hagander" <mha@sollentuna.net>
Re: Table Spaces
Magnus Hagander wrote:
> >>If you run NTFS, it's still possible to use arbitrary links. 
> >In the Windows
> >>world, they are called junctions. Microsoft does not provide 
> >a junction tool
> >>for some reason (perhaps because it's limited to NTFS). A 
> >good tool, free
> >>and with source, can be found here
> >>http://www.sysinternals.com/ntw2k/source/misc.shtml#junction 
> >I use this tool
> >>myself. Works like a charm.
> >>
> >>  
> >>
> >
> >We've looked at it before. Apart from anything else I don't think its 
> >license is compatible with PostgreSQL's.
> 
> Well, people can still use it. We just can't distribute it... We can
> always link to it.
> But unless there is a GUI tool (actually, unless it shows up in the
> *default* GUI tool), expect there to be questions. An 

I assume we can just look at the source and write our own version
bypassing any license.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Mon, 17 May 2004 19:04:24 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: Table Spaces
> Magnus Hagander wrote:
>> >>If you run NTFS, it's still possible to use arbitrary links.
>> >In the Windows
>> >>world, they are called junctions. Microsoft does not provide
>> >a junction tool
>> >>for some reason (perhaps because it's limited to NTFS). A
>> >good tool, free
>> >>and with source, can be found here
>> >>http://www.sysinternals.com/ntw2k/source/misc.shtml#junction
>> >I use this tool
>> >>myself. Works like a charm.
>> >>
>> >>
>> >>
>> >
>> >We've looked at it before. Apart from anything else I don't think its
>> >license is compatible with PostgreSQL's.
>>
>> Well, people can still use it. We just can't distribute it... We can
>> always link to it.
>> But unless there is a GUI tool (actually, unless it shows up in the
>> *default* GUI tool), expect there to be questions. An
>
> I assume we can just look at the source and write our own version
> bypassing any license.

I wouldn't be so sure about that. If this insane SCO crap has taught me
anything, the PostgreSQL should have a defined and legally vetted process
for duplicating functionality. ala' phoenix BIOS.

What would be good is a "contaminated" developer specifying functionality,
and detailing the various APIs needed (documenting the undocumented ones
as nessisary) while someone else writes the code. It is the *only* legal
unemcumbered methodology that will work.



Tue, 18 May 2004 10:55:58 -0400 (EDT)
pgsql@mohawksoft.com
Re: Table Spaces