When paging through data that comes from a DB, you need to know how many pages there will be to render the page jump controls.
Currently I do that by running the que
Since Postgres already does a certain amount of caching things, this type of method isn't as inefficient as it seems. It's definitely not doubling execution time. We have timers built into our DB layer, so I have seen the evidence.