From: Kenneth Marshall <ktm@rice.edu>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Derrick Rice <derrick.rice@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Updating histogram_bounds after a delete
Date: Thu, 17 Mar 2011 09:55:29 -0500
Message-ID: <20110317145529.GK11541@aart.is.rice.edu> (raw)
In-Reply-To: <4D81D939020000250003BA22@gw.wicourts.gov>
References: <AANLkTik6FnXpdEF+edr7Jh-cmEUfjsaPRoGOmMaxxPFO@mail.gmail.com>
<4D80EBAB020000250003B9DE@gw.wicourts.gov>
<AANLkTikrVqwXp3ugoMLR8-6BOegSDByRCuTCFtGVBZ+E@mail.gmail.com>
<4D81D939020000250003BA22@gw.wicourts.gov>
On Thu, Mar 17, 2011 at 09:49:45AM -0500, Kevin Grittner wrote:
> Derrick Rice <derrick.rice@gmail.com> wrote:
> > Kevin Grittner <Kevin.Grittner@wicourts.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ktm@rice.edu, Kevin.Grittner@wicourts.gov, derrick.rice@gmail.com
Subject: Re: Updating histogram_bounds after a delete
In-Reply-To: <20110317145529.GK11541@aart.is.rice.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox