I can't get through to you because your spam filter blocks my SMTP relay. Tom Lane wrote: > > > I now have a quite similar problem: while a CURSOR on a SELECT for a > > normal query works now, I encounter the same behavior for aggregate > > queries: > > As I think I pointed out in the original discussion, backwards fetch > doesn't work for most plan types more complex than a simple sequential > or index scan. This is not trivial to fix. > > regards, tom lane
I've looked trough our exchange on the list, but there's nothing about that. I found another posting which I guess you mean (http://archives.postgresql.org/pgsql-novice/2002-12/msg00222.php). I have put a comment in the interactive documentation for now, quoting your original mail. This really should be in the distributed documentation for FETCH. So can I be sure that every non-aggregate SELECT on tables joined with unique indexes works, independent of the WHERE or ORDER BY? Is anybody working on implementing this functionality? Thanks, Florian Wunderlich ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
