Skip site navigation (1) Skip section navigation (2)

Re: win32 tablespace handing

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Reini Urban" <rurban(at)x-ray(dot)at>,"PostgreSQL Developers" <pgsql-hackers(at)postgresql(dot)org>
Cc: <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: win32 tablespace handing
Date: 2004-10-05 18:13:00
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE456A0A@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32
>> Cygwin can do symlinks for directories via the magic .lnk file.
>> But Cygwin can also do junctions via hardlinks in ln.exe.
>> I thought link() calls the junction code.
>> I'll investigate why the libc link() failed, and if ln.exe does some 
>> sifferent magic, similar to pgsymlink.
>
>I thought a little bit over this.
>
>hardlinks and junctions don't work across physical disks, only 
>symlinks.

Pardon me for saying "Huh"? Junctions work just fine across disks. I
just created a tablespace here, and got the following from the
sysinternals too:
D:\pgdata\pg_tblspc>junction 164705

Junction v1.03 - Win2K junction creator and reparse point viewer
Copyright (C) 2000-2002 Mark Russinovich
Systems Internals - http://www.sysinternals.com

D:\pgdata\pg_tblspc\164705: JUNCTION
   Substitute Name: c:\temp\pgtest


And yes, tables created there go on C:. Tables in the default tablespace
go on D:.


(IIRC, junctions are even used for the Remote Storage facility, so the
disk theoreticallky doesn't even have to be in your machine at the time)


I don't think hardlinks work across disks, though, but I don't think we
use them.


//Magnus

pgsql-hackers by date

Next:From: Reini UrbanDate: 2004-10-05 18:56:17
Subject: Re: win32 tablespace handing
Previous:From: Bruce MomjianDate: 2004-10-05 17:59:38
Subject: Re: win32 tablespace handing

pgsql-hackers-win32 by date

Next:From: Reini UrbanDate: 2004-10-05 18:56:17
Subject: Re: win32 tablespace handing
Previous:From: Bruce MomjianDate: 2004-10-05 17:59:38
Subject: Re: win32 tablespace handing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group