Reindexing the index also fixes the problem, but regular reindexing cannot be a
solution, since there is still a timeframe where wrong results are returned.
I've made a copy of the index-file when it was broken, after the update and
after reindexing. Is there a tool for getting a human-readable dump of the
index?
You can play with gevel module
http://www.sai.msu.su/~megera/postgres/gist/
http://www.sai.msu.su/~megera/postgres/gist/gevel/README.gevel
Using PostgreSQL 8.1.4 with ltree version from CVS (since there's another bug
fixed in CVS). Problem occurs on a 2 node cluster of 2 Quad-CPU system (Xeon, 2
physical CPU's, 2 hyperthreading), one node running the database, the other one
the webserver.
Any ideas?
Oops, wait a bit: problem is founded in gist_between() call.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
