Re: index scan leads to result that is different from sec scan after upgrading to 8.3.4

From: "Sergey Konoplev" <gray(dot)ru(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: index scan leads to result that is different from sec scan after upgrading to 8.3.4
Date: 2008-10-20 14:07:00
Message-ID: c3a7de1f0810200707g25b7c890r552a83f15af580ad@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> "Sergey Konoplev" <gray(dot)ru(at)gmail(dot)com> writes:
>> Will somebody explain what has happened and how to solve the problem please?
>
> Apparently you've found a bug in either btree_gist or the core GIST
> code. Can you put together a self-contained test case?
>

Ok, I will try.

One more thing I want to mention is that we have fixed (temporary) the
problem by recreating the index without "where" clause so it is not
used by the queries now.

--
Regards,
Sergey Konoplev
--
PostgreSQL articles in english & russian
http://gray-hemp.blogspot.com/search/label/postgresql/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Lennin Caro 2008-10-20 14:08:03 Re: removing a portion of text
Previous Message Tom Lane 2008-10-20 13:32:26 Re: index scan leads to result that is different from sec scan after upgrading to 8.3.4