Re: Slow query - possible bug?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gavin Hamill <gdh(at)laterooms(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Slow query - possible bug?
Date: 2006-04-18 19:51:44
Message-ID: 18448.1145389904@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Gavin Hamill <gdh(at)laterooms(dot)com> writes:
> On Tue, 18 Apr 2006 13:31:48 -0400
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> There should be a fix for this by the time PG 8.2 comes out, but in
>> the meantime you might find that it helps to write the range check in
>> a way that doesn't have identical bounds, eg
>> date >= '2006-06-10'::date AND date < '2006-06-11'::date

> OK coolies - we've already had a code release for this (and other
> stuff) planned for tomorrow morning checking on the client side
> if a single date has been chosen, then do an equality test on that...

Fair enough, no reason to replace one workaround with another. But
would you try it on your test case, just to verify the diagnosis?

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jim C. Nasby 2006-04-18 19:56:01 Re: index is not used if I include a function that returns current time in my query
Previous Message Gavin Hamill 2006-04-18 19:08:39 Re: Slow query - possible bug?