RE: problem about full scan temporary table

  • From: Tanel Poder <tanel.poder.003@xxxxxxx>
  • To: binhpham15@xxxxxxxxxxx, jonathan@xxxxxxxxxxxxxxxxxx, wqhhp@xxxxxxxxx, oracle-l@xxxxxxxxxxxxx
  • Date: Sun, 24 Sep 2006 23:36:30 +0800

Temporary tablespace space is managed differently than normal tablespaces.
They use some in-memory maps for that, thus allocating new extents shouldn't
be much of an overhead.


From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Binh Pham
Sent: Sunday, September 24, 2006 23:18
To: jonathan@xxxxxxxxxxxxxxxxxx; wqhhp@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: problem about full scan temporary table


If someone wants to load lots of data into the GTT, based on the 1M extent
size, doesn't this seem to be inefficient and may pose a performance issue
due to Oracle has to keep extending?  I guess that if one wants to load lots
of data (i.e. 1G+ data) into GTT, there might be other options rather than

Other related posts: