| From: | Kenneth Marshall <ktm(at)rice(dot)edu> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Derrick Rice <derrick(dot)rice(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Updating histogram_bounds after a delete |
| Date: | 2011-03-17 14:55:29 |
| Message-ID: | 20110317145529.GK11541@aart.is.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Mar 17, 2011 at 09:49:45AM -0500, Kevin Grittner wrote:
> Derrick Rice <derrick(dot)rice(at)gmail(dot)com> wrote:
> > Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov wrote:
> >
> >> there is a feature to probe the end of an index's range in
> >> situations where data skew was often causing less than optimal
> >> plans to be chosen.
> >
> > Was this introduced in 9.0 or was it earlier?
>
> I don't remember when it was added. I took a stab at searching for
> it, but didn't get it figured out; if nobody who knows off-hand
> jumps in, I'll try again when I have more time.
>
I think this is it:
http://archives.postgresql.org/pgsql-committers/2010-01/msg00021.php
Regards,
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-03-17 15:00:59 | Re: Updating histogram_bounds after a delete |
| Previous Message | Kevin Grittner | 2011-03-17 14:49:45 | Re: Updating histogram_bounds after a delete |