Lists: | pgsql-hackerspgsql-hackers-win32 |
---|
From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
---|---|
To: | <jearl(at)bullysports(dot)com>, <tswan(at)idigx(dot)com> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Greg Stark" <gsstark(at)mit(dot)edu>, <pgsql-hackers(at)postgresql(dot)org>, "PostgreSQL Win32 port list" <pgsql-hackers-win32(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Tablespaces |
Date: | 2004-03-05 09:20:21 |
Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA40184D008@m0114.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers pgsql-hackers-win32 |
> First of all, symlinks are a pretty popular "feature." Even Windows
> supports what would be needed. Second of all, PostgreSQL will still
> run on OSes without symlinks, tablespaces won't be available, but
> PostgreSQL will still run. Since we are all using PostgreSQL without
My idea for platforms that don't support symlinks would be to simply create
a tblspaceoid directory inplace instead of the symlink (maybe throw a warning).
My feeling is, that using the same syntax on such platforms is important,
but actual distribution is not (since they will most likely be small systems).
Andreas
From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at> |
Cc: | jearl(at)bullysports(dot)com, tswan(at)idigx(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org, PostgreSQL Win32 port list <pgsql-hackers-win32(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Tablespaces |
Date: | 2004-03-05 14:48:32 |
Message-ID: | 200403051448.i25EmWF04964@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers pgsql-hackers-win32 |
Zeugswetter Andreas SB SD wrote:
>
> > First of all, symlinks are a pretty popular "feature." Even Windows
> > supports what would be needed. Second of all, PostgreSQL will still
> > run on OSes without symlinks, tablespaces won't be available, but
> > PostgreSQL will still run. Since we are all using PostgreSQL without
>
> My idea for platforms that don't support symlinks would be to simply create
> a tblspaceoid directory inplace instead of the symlink (maybe throw a warning).
> My feeling is, that using the same syntax on such platforms is important,
> but actual distribution is not (since they will most likely be small systems).
Nice idea --- so you can create tablespaces, but can't specify a
different location for it --- makes sense.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073