| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Thomas Swan <tswan(at)idigx(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Tablespaces |
| Date: | 2004-03-04 02:41:17 |
| Message-ID: | 200403040241.i242fHI05299@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-hackers-win32 |
Thomas Swan wrote:
> >The advantage of symlinks is that an administrator could see how things
> >are laid out from the command line.
> >
> >
> >
> That's a poor reason to require symlinks. The administrator can just as
> easily open up psql and query pg_tablespace to see that same
> information. Besides, the postgres doesn't know where to look on the
> filesystem for the /path/to/oid without a system catalog lookup. There
> doesn't seem to be any sensible reason to force a filesystem requirement
> when the core operations are diffferent to begin with.
>
> If a more global view of all databases is necessary, perhaps there ought
> to be a system wide view which could display all of that information at
> once: dbname, relation name, and physical location.
Who doesn't have symlinks these days, and is going to be using
tablespaces? Even Win32 has them.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-04 03:11:11 | 7.4.2 branding |
| Previous Message | Thomas Swan | 2004-03-04 02:31:16 | Re: Tablespaces |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-03-04 04:14:51 | Re: Tablespaces |
| Previous Message | Thomas Swan | 2004-03-04 02:31:16 | Re: Tablespaces |