Skip site navigation (1) Skip section navigation (2)

RE: Big 7.1 open items

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:15:39
Message-ID: 8F4C99C66D04D4118F580090272A7A23018C36@SECTORBASE1 (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> > 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

We could create /data/databases/DATABASEOID/ and create soft-links to
table-files. This way different tables of the same database could be in
different tablespaces. /data/database path would be used in production
and /data/tablespace path would be used in recovery.



pgsql-hackers by date

Next:From: Tom LaneDate: 2000-06-26 22:33:56
Subject: Re: 'natural join' core dump
Previous:From: Jenni JaegerDate: 2000-06-26 22:13:43
Subject: connection to Access tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group