Re: GLOBAL vs LOCAL temp tables

Alvaro Herrera wrote:
> On Wed, Apr 16, 2003 at 10:09:38AM +0900, Tatsuo Ishii wrote:
> > The real problem with current temp tables is the implementation. I see
> > very quick growth of system catalogs with heavy use of temp
> > tables(some hundred mega bytes per week on a busy system for
> > example). To fix the system catalogs, we have to stop postmaster and
> > have to do reindex. This is truly a pain.
> 
> This is fixed in 7.4 already.  It wasn't a problem with temp tables, but
> with btree indexes.

Yes, it is fixed partly, but I want to point out that the fix somewhat
asymetric.

For example, it would be nice to tell people that they should either use
VACUUM several times a day _or_ run VACUUM FULL nightly.  The problem
with this simplification is indexes --- VACUUM records free indx pages,
while VACUUM FULL doesn't do anything with empty index pages.

Is there anything we can do to improve this situation?  Should VACUUM
FULL record free index pages?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073