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

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>, "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:47:57
Message-ID: 48FC9A1D.6000507@sigaev.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Hmm. So the problem seems to be statable as "a full-index scan on a
> GIST index might fail to return all the rows, if the index has been
> modified since creation". Teodor, can you think of anything you
> changed recently in that area?

Only fixing possible duplicates during index scan. Will see.

--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martin Gainty 2008-10-20 14:56:10 Re: Annoying Reply-To
Previous Message Andrei Kovalevski 2008-10-20 14:14:35 Re: [ODBC] Error in Adding All Table