From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
Subject: | Re: Big 7.1 open items |
Date: | 2000-06-21 05:19:29 |
Message-ID: | 39505061.F42334AB@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> Yes, I didn't like the environment variable stuff. In fact, I would
> like to not mention the symlink location anywhere in the database, so
> it can be changed without changing it in the database.
Well, as y'all have noticed, I think there are strong reasons to use
environment variables to manage locations, and that symlinks are a
potential portability and robustness problem.
An additional point which has relevance to this whole discussion:
In the future we may allow system resource such as tables to carry names
which use multi-byte encodings. afaik these encodings are not allowed to
be used for physical file names, and even if they were the utility of
using standard operating system utilities like ls goes way down.
istm that from a portability and evolutionary standpoint OID-only file
names (or at least file names *not* based on relation/class names) is a
requirement.
Comments?
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-21 05:23:57 | Re: Big 7.1 open items |
Previous Message | Don Baccus | 2000-06-21 05:16:50 | Re: Big 7.1 open items |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-21 05:23:57 | Re: Big 7.1 open items |
Previous Message | Don Baccus | 2000-06-21 05:16:50 | Re: Big 7.1 open items |