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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Sergey Konoplev" <gray(dot)ru(at)gmail(dot)com>
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 13:17:06
Message-ID: 27870.1224508626@sss.pgh.pa.us
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?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sergey Konoplev 2008-10-20 13:17:21 Re: index scan leads to result that is different from sec scan after upgrading to 8.3.4
Previous Message Sergey Konoplev 2008-10-20 13:11:21 index scan leads to result that is different from sec scan after upgrading to 8.3.4