From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | AW: OK, OK, Hiroshi's right: use a seperately-generated filename |
Date: | 2000-06-19 13:46:22 |
Message-ID: | 219F68D65015D011A8E000006F8590C605BA5978@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> It's better than *all* segments of tables in one directory, which is
> what you get if the segment number is just a component of a flat file
> name. We have to have a better answer than that for people who need
> to cope with tables bigger than a disk. Perhaps someone can
> think of a
> better answer than subdirectory-per-segment-number, but I think that
> will work well enough; and it doesn't add any complexity for file
> access.
I do not see this connection between a filesystem and a disk ?
Modern systems have the ability to join more than one disk into
one filesystem.
Also if we think about separating large tables into smaller parts
we imho want something where the optimizer has knowledge
what data it finds in what part of the table.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-06-19 14:09:31 | Re: [BUGS] libpq++ update |
Previous Message | Bruce Momjian | 2000-06-19 13:30:56 | Re: Big 7.1 open items |