>> Maybe we could only put the temp files in a different directory.
>> They are where performance matters.
>> If a normal table create takes a few seconds that is not a
>> real problem.
Once you have the ability to create tablespaces, you can modify the temp
table thingy a little to create temporary tables in the temp tablespace. If
there is no explicit temp tablespace defined, then it defaults to the system
tablespace (which is where it goes now anyway).
What this means is that tablespaces must have a flag indicating whether or
not they are the temp tablespace or not (only one per database). Also, it's
handy to have a default tablespace for each user, so that tables are created
in whichever tablespace is the default for that user, unless they explicitly
state which tablespace to use.
>>
>> > We could actually
>> > hash the file names into directory buckets and access them
>> > that way, and have one directory that old symlinks to the
>> > hashed files.
I don't think this is necessary, because if you have a system that requires
this kind of action, then the administrator can create a temp tablespace
which is used for all the temporary tables, and spread the rest of the
tables and indices among the remaining tablespaces.
MikeA
