pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Merlin Moncure <mmoncure@gmail.com>
To: Andreas Kretschmer <akretschmer@spamfence.net>
Cc: pgsql-performance@postgresql.org, "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Cc: postgres hackers <pgsql-hackers@postgresql.org>
Subject: Re: [PERFORM] BETWEEN optimizer problems with single-value range
Date: Wed, 15 Mar 2006 17:11:16 -0500
Message-ID: <b42b73150603151411h293c4942v160960aaa8c9cd1e@mail.gmail.com> (raw)
In-Reply-To: <20060315204700.GA17623@KanotixBox>
References: <44180105.EE98.0025.0@wicourts.gov>
	<b42b73150603151136wd1a8b1dw6e03d39f07fd6cb@mail.gmail.com>
	<20060315204700.GA17623@KanotixBox>

On 3/15/06, Andreas Kretschmer <akretschmer@spamfence.net> wrote:
> Merlin Moncure <mmoncure@gmail.com> schrieb:
>
> > On 3/15/06, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
> > > Attached is a simplified example of a performance problem we have seen,
> > > with a workaround and a suggestion for enhancement (hence both the
> > > performance and hackers lists).
> >
> >
> > Hi Kevin.  In postgres 8.2 you will be able to use the row-wise
>
> 8.2? AFAIK, Feature freeze in juni/juli this year...
> Release august/september.

yes, but I was addressing kevin's point about enhancing the server...

> > comparison for your query which  should guarantee good worst case
> > performance without having to maintain two separate query forms.  it
>
> Perhaps, a bitmap index scan (since 8.1) are useful for such querys.
> Thats why i asked which version.

I think you will find that reading a range of records from a table
ordered by an index utilizing the 8.2 comparison feature is much
faster than a bitmap index scan.

Merlin



view thread (20+ messages)  latest in thread

Message-ID: <b42b73150603151411h293c4942v160960aaa8c9cd1e@mail.gmail.com>
Permalink:  ../b42b73150603151411h293c4942v160960aaa8c9cd1e@mail.gmail.com/
Also on:    postgresql.org/message-id/b42b73150603151411h293c4942v160960aaa8c9cd1e@mail.gmail.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: mmoncure@gmail.com, akretschmer@spamfence.net, Kevin.Grittner@wicourts.gov, pgsql-hackers@postgresql.org
  Subject: Re: [PERFORM] BETWEEN optimizer problems with single-value range
  In-Reply-To: <b42b73150603151411h293c4942v160960aaa8c9cd1e@mail.gmail.com>
  References: <44180105.EE98.0025.0@wicourts.gov> <b42b73150603151136wd1a8b1dw6e03d39f07fd6cb@mail.gmail.com> <20060315204700.GA17623@KanotixBox> <b42b73150603151411h293c4942v160960aaa8c9cd1e@mail.gmail.com>

* 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