Mike Aubury <mike(dot)aubury(at)aubit(dot)com> writes:
> ie - under postgresql it appears we've scrolled *past* the last row and need
> an additional fetch to get back to our last row..
Why do you find that surprising? It seems to me to be symmetrical with
the case at the beginning of the table --- the cursor is initially
positioned before the first row. Why shouldn't there be a corresponding
state where it's positioned after the last row?
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-04-01 15:00:15|
|Subject: Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong |
|Previous:||From: Tom Lane||Date: 2008-04-01 14:50:32|
|Subject: Re: build multiple indexes in single table pass? |