| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
| Cc: | "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, 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-26 22:03:42 |
| Message-ID: | 19330.962057022@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> writes:
> Do we need *both* database & tablespace to find table file ?!
> Imho, database shouldn't be used...
That'd work fine for me, but I think Bruce was arguing for paths that
included the database name. We'd end up with paths that go something
like
..../data/tablespaces/TABLESPACEOID/RELATIONOID
(plus some kind of decoration for segment and version), so you'd have
a hard time telling which files in a tablespace belong to which
database. Doesn't bother me a whole lot, personally --- if one wants
to know that one could just as well assign separate tablespaces to
different databases. They're only subdirectories anyway...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jenni Jaeger | 2000-06-26 22:13:43 | connection to Access tables |
| Previous Message | Giles Lean | 2000-06-26 21:36:53 | Re: C exception code |