>> The application is returning 300,000 records in some SELECT clause (a
>> ResultSet) this finish the client's JVM memory, so my solution to this
>> was to use the SELECT's LIMIT clause returning 600 records and making
>> the internal logic that when the user gets past the 600th record the
>> application automatically issues another query with LIMIT and OFFSET
>> clauses causing a little delay but this is better than finishing the
>> memory in the client's machine (if you know a better solution or have
>> some advices, please let me know).
I'm surprised no one has yet suggested using a cursor.
regards, tom lane
