Re: Table Spaces
От | Magnus Hagander |
---|---|
Тема | Re: Table Spaces |
Дата | |
Msg-id | 6BCB9D8A16AC4241919521715F4D8BCE34BA2A@algol.sollentuna.se обсуждение исходный текст |
Ответ на | Table Spaces (Gavin Sherry <swm@linuxworld.com.au>) |
Ответы |
Re: Table Spaces
|
Список | pgsql-hackers |
>>>>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
В списке pgsql-hackers по дате отправления: