On Tue, Jun 16, 2009 at 4:36 PM, Tom Lane<t...@sss.pgh.pa.us> wrote: > Actually the easiest way to fix that is to get rid of the LIMIT. > (Maybe use a cursor instead, and fetch only twenty rows.) LIMIT > magnifies the risks from any estimation error, and you've got a lot > of that here ...
There's no cursor support in ActiveRecord, the ORM library we use, and I'm not going to write it. Anyway, I would prefer not to gloss over the underlying problem with something that requires a "TODO" next to it. What can be done to fix the underlying problem? Nothing? A. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
