| From: | Mark Cave-Ayland <mark(dot)cave-ayland(at)siriusit(dot)co(dot)uk> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Missing results from scroll cursor in PostgreSQL 8.3.3? |
| Date: | 2008-09-25 15:21:32 |
| Message-ID: | 48DBAC7C.4020200@siriusit.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi there,
Following up a report on the PostGIS bugtracker (also submitted to
pgsql-bugs here:
http://archives.postgresql.org/pgsql-bugs/2008-09/msg00086.php), I'm
wondering if there is a bug in the way that GiST indexes interact with
scroll cursors.
I've managed to reproduce the bug using btree_gist rather than PostGIS
and have attached a test case for review. The key point is that if a
GiST index is used to pull results from a scroll cursor then "FETCH
ABSOLUTE X" fails to return any rows. I'm wondering if it could be
related to the fact the GiST indexes are not ordered? Perhaps the only
thing that is wrong is that a suitable ERROR message is missing?
ATB,
Mark.
--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063
| Attachment | Content-Type | Size |
|---|---|---|
| gist_cursor_scroll.sql | text/plain | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2008-09-25 15:42:03 | Re: Add default_val to pg_settings |
| Previous Message | Mark Mielke | 2008-09-25 15:10:44 | Re: PostgreSQL future ideas |