I would pull your prod data down locally and play with the queries to optimize them in your local postgres. (rule out any difference in behavior on the heroku stack)
grab your explain output and throw it in http://explain.depesz.com/ if your conditions are easy, you can add a uniqueness constraint at the db level, which would be faster than doing it at the ORM/application level. On Fri, Jun 24, 2011 at 6:08 AM, Michel Pigassou <[email protected]> wrote: > Actually the query itself contains some restrictions, like the date and the > owner of the objet, so it does not take so long to run. > But I'll keep searching :) > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/heroku/-/3WN0_grxrz4J. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- -John -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
