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

Re: Missing results from scroll cursor in PostgreSQL 8.3.3?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Cave-Ayland <mark(dot)cave-ayland(at)siriusit(dot)co(dot)uk>
Cc: pgsql-hackers(at)postgresql(dot)org, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: Missing results from scroll cursor in PostgreSQL 8.3.3?
Date: 2008-09-25 16:27:49
Message-ID: 8229.1222360069@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
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: 
> 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 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.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2008-09-25 17:06:27
Subject: Re: Proposal: move column defaults into pg_attributealong with attacl
Previous:From: Simon RiggsDate: 2008-09-25 16:27:21
Subject: Re: get_relation_stats_hook()

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