| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, 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-16 16:54:00 |
| Message-ID: | 7747.961174440@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
>> ... But I think it's critical to keep
>> the low-level file access protocol simple and reliable, which really
>> means minimizing the amount of information the backend needs to know
>> to figure out which file to write a page in. With something like the
>> above you only need to know the tablespace name (or more likely OID),
>> the relation OID (+name or not, depending on outcome of other
>> argument), and the offset in the table. No worse than now from the
>> software's point of view.
>> Comments?
> I'm probably missing the context a bit, but imho we should try hard to
> stay away from symlinks as the general solution for anything.
Why?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2000-06-16 16:58:03 | Re: AW: Big 7.1 open items |
| Previous Message | The Hermit Hacker | 2000-06-16 16:52:27 | Re: Big 7.1 open items |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-16 17:08:38 | Re: Big 7.1 open items |
| Previous Message | The Hermit Hacker | 2000-06-16 16:52:27 | Re: Big 7.1 open items |