Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Vacuuming of indexes on tables.


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: elein <elein(at)varlena(dot)com>
  • Cc: pgsql-general(at)postgresql(dot)org
  • Subject: Re: Vacuuming of indexes on tables.
  • Date: Tue, 18 Apr 2006 15:44:49 -0400
  • Message-id: <18369(dot)1145389489(at)sss(dot)pgh(dot)pa(dot)us>

elein <elein(at)varlena(dot)com> writes:
> The order of events seems to be vacuum indexes and then vacuum the
> table.  Wouldn't we get more bang if we vacuumed the table and then
> the indexes?

No, the problem is that we can't recycle removed index pages until we
are certain there are not any transactions referencing or about to
reference the pages.  Postponing the recycle to a later command seems
the only very practical way to deal with that --- you don't want VACUUM
hanging up waiting for transactions that may or may not finish any time
soon.  See the notes in access/nbtree/README.

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group