Skip site navigation (1) Skip section navigation (2)

Re: Missing results from scroll cursor in PostgreSQL8.3.3?

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mark Cave-Ayland <mark(dot)cave-ayland(at)siriusit(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: Missing results from scroll cursor in PostgreSQL8.3.3?
Date: 2008-09-25 17:56:54
Message-ID: 1222365414.4445.823.camel@ebony.2ndQuadrant (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Thu, 2008-09-25 at 12:27 -0400, Tom Lane wrote:
> Mark Cave-Ayland <mark(dot)cave-ayland(at)siriusit(dot)co(dot)uk> writes:
> > Following up a report on the PostGIS bugtracker (also submitted to 
> > pgsql-bugs here: 
> >, I'm 
> > wondering if there is a bug in the way that GiST indexes interact with 
> > scroll cursors.
> I remember Teodor remarking that there's some problem with fetching
> backwards in a GIST indexscan, but I don't know the details --- in
> particular, no idea whether it's fixable or we need to put in something
> to prevent trying it.  The latter would be a bit of a PITA since right
> now indexscans are assumed to support backwards scan regardless of
> index type.

Does ABSOLUTE 3 do a backward scan? Hope not. Just rewind and forward
scan. Presumably the bug is present when you don't do ABSOLUTE -1 first?

Seems like GIST should be able to fake a backwards scan if needed.

 Simon Riggs 
 PostgreSQL Training, Services and Support

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2008-09-25 18:01:45
Subject: Re: Missing results from scroll cursor in PostgreSQL 8.3.3?
Previous:From: Dmitry KoterovDate: 2008-09-25 17:39:44
Subject: Re: Review Report: propose to include 3 new functions into intarray and intagg

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group