Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I'm not sure that I see the point of this at all.  ISTM the entire
>> reason for using a cursor is that you're going to fetch the results
>> in bite-size pieces.  I don't see the current Postgres source code
>> surviving into the era where >2G rows is considered bite-size ;-)

> Think MOVE to a specific section of the cursor > 2gig.  I can see that
> happening.

Yeah, and by the time it happens you'll have gotten bored and found
something else to do.  With no support in the system for random access
to a cursor result, this is just about as useless as the FETCH case.

In any case I agree with Alvaro's comment: the way to support int8 in
a FETCH/MOVE command is not to try to convert the entire rest of the
grammar to int8 instead of int4 as its native datatype.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

Reply via email to