> > That's gonna have to be fixed. If you're not up for it, don't implement
> > this. Given that cursors (are supposed to) support FETCH BACKWARDS,
> > I really don't see why they shouldn't be expected to handle ReScan...
> I thought only scrollable cursors can do that. What if cursor isn't
> scrollable? Should it error during the execution?
In PostgreSQL, all cursors are scrollable. The allowed grammar keyword is
simply ignored. I am actually not sure that this is optimal, since there
are a few very effective optimizations, that you can do if you know, that
ReScan is not needed (like e.g. not storing the result temporarily).
Andreas
