| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Mario Weilguni <mweilguni(at)sime(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Subject: | Re: Another Ltree/GiST problem |
| Date: | 2006-08-07 16:55:24 |
| Message-ID: | 44D7707C.3010004@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-08-07 16:56:40 | Re: pg_upgrade (was: 8.2 features status) |
| Previous Message | Lukas Smith | 2006-08-07 16:52:44 | Re: 8.2 features status |