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: 2006-04-18 19:44:49
Message-ID: 18369.1145389489@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dilan A 2006-04-18 20:03:41 Permission problem opening database
Previous Message Tom Lane 2006-04-18 19:21:10 Re: Weird error updating table