Re: Skipping VACUUM of indexes when no work required

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Skipping VACUUM of indexes when no work required
Date: 2006-02-11 21:36:03
Message-ID: 27701.1139693763@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> I believe this is safe.

I won't insult your intelligence by pointing out how I know that you
didn't even test the patch against hash or gist.

The major problem with the patch is that it's incapable of producing
correct tuple-count stats for partial indexes, which is really not
acceptable from a planning standpoint. What I'm currently fooling with
is skipping the bulkdelete scan only if the index isn't partial...

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-02-11 21:57:15 Re: TODO item -- Improve psql's handling of multi-line
Previous Message Jim C. Nasby 2006-02-11 19:57:54 Re: Scrollable cursors and Sort performance