Re: [PERFORM] Slow query: bitmap scan troubles - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [PERFORM] Slow query: bitmap scan troubles
Date
Msg-id CA+U5nML7drGt_5k3X1jH0XLs+qyhsiT7xy0VRs2Nixm_DRdTUg@mail.gmail.com
Whole thread Raw
In response to Re: [PERFORM] Slow query: bitmap scan troubles  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On 6 January 2013 16:29, Jeff Janes <jeff.janes@gmail.com> wrote:

> Worse, this over-punishment of bloat is more likely to penalize partial
> indexes.  Since they are  vacuumed on the table's schedule, not their own
> schedule, they likely get vacuumed less often relative to the amount of
> turn-over they experience and so have higher steady-state bloat. (I'm
> assuming the partial index is on the particularly hot rows, which I would
> expect is how partial indexes would generally be used)

That's an interesting thought. Thanks for noticing that.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [PERFORM] Slow query: bitmap scan troubles
Next
From: Tom Lane
Date:
Subject: Re: [PERFORM] Slow query: bitmap scan troubles