All temporary segment creation operations are inherently NOLOGGING, so
tablespaces with TEMPORARY contents are effectively NOLOGGING too, whether or
not they are defined as such in the data dictionary. Of course, this only
applies to datafile tablespaces, because tempfile tablespaces cannot be defined
as LOGGING at all.


-----Original Message-----
Sent: Sunday, 3 September 2000 8:29


I guess the question says it all, really: do sorts go any faster when they
are being written down to proper temporary tablespace if that tablespace has
been created (or altered to be) NOLOGGING?

I imagine that in turn comes down to what actually happens when the PGA gets
written out to disk.  If it's a bunch of conventional inserts, then
nologging wouldn't do anything.  If it's more like a direct load insert, I
can see that it might make a difference.

Anyway: anything significant to be gained by doing it?  Any nasty 'gotchas'
you can think of?