> -----Original Message-----
> From: pgsql-hackers-owner(at)hub(dot)org [mailto:pgsql-hackers-owner(at)hub(dot)org]On
> Behalf Of Bruce Momjian
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > > We have this in the CURSOR documentation:
> > > Once all rows are fetched, every other fetch access
> > > returns no rows.
> > > Is this still true?
> > Not if you then move or fetch backwards, I should think...
> No, it works. I think Tatsuo fixed it. After a FETCH ALL, I did this,
> and it worked:
This is true and false.
For index scan I fixed it before 6.5 and for sequential scan
I fixed it before 7.0.
However there remains some type of scan that returns no rows
after hitting end.
Especially for GROUP BY,*fetch backward* doesn't work well
fundamentally. I have known this but I've never seen bug
reports for this. It's not so easy to fix this and it wouldn't be
an effective way to scan base relation again for *GROUP BY*.
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2000-04-05 00:05:41|
|Subject: Re: ERROR: No one parent tuple was found |
|Previous:||From: Bruce Momjian||Date: 2000-04-04 20:47:19|
|Subject: Re: Indexes growing continuously|