"Martijn Tonies" <m.tonies@...> wrote:

>
> Doesn't it make more sense to get a useful query cache?

Then we may forget about being a small footprint database. Unlike most of
other databases, FB almost never (unless this is unavoidable, like sorting)
keeps internal row buffers. Rows are fetched from disk one by one and the
only optimization is the client side batch fetch to save protocol
round-trips. Any kind of implicit (not requested by user) per statement
dataset caching brings the memory usage too high, IMO. As for the FIRST/SKIP
problem, I'd say this is easily solvable on the client or in PSQL via an
open cursor and explicit fetches. Do I miss something important in this
wish?


Dmitry