| From: | "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Alternative database locations are broken |
| Date: | 2000-11-05 06:09:16 |
| Message-ID: | 017c01c046ee$edf39be0$b87a30d0@sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> >> I think that to handle locations we could symlink catalogs - ln -s
> >> path_to_database_in_some_location .../base/DatabaseOid
>
> > But that's a kludge. We ought to discourage people from messing with the
> > storage internals.
>
> It's not a kluge, it's a perfectly fine implementation. The only kluge
> here is if people have to reach in and establish such symlinks by hand.
> We want to set up a user interface that hides the implementation.
Agreed. And I don't see problems with handling this at CREATE DATABASE
time. Create database dir in specified location, create symlink from
base dir and remember location name in pg_database.datpath.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2000-11-05 07:02:19 | v7.0.3 *pre-release* ... |
| Previous Message | Vadim Mikheev | 2000-11-05 05:59:00 | Re: Transaction ID wraparound: problem and proposed solution |