On Wed, May 29, 2013 at 11:47 PM, Jack Royal-Gordon wrote:
> Tonight, I started getting "out of memory" errors from several different
> queries, many of which are simple, and all of which have worked well in the
> past. For example, a simple "select" across several hundred rows that should
> p
Tonight, I started getting "out of memory" errors from several different
queries, many of which are simple, and all of which have worked well in the
past. For example, a simple "select" across several hundred rows that should
produce 20 rows or less gets this error. App has not been touched in
Can we please have an update from Heroku on whether we need to migrate to
someone else's addon ASAP, too, before the addon decides to stop responding
to memcache read/writes? :)
On Wed, May 29, 2013 at 5:53 PM, Daniel Farina wrote:
> On Wed, May 29, 2013 at 2:48 PM, wrote:
> > Hello,
> >
> > I
On Wed, May 29, 2013 at 2:48 PM, wrote:
> Hello,
>
> I am attempting to add memcache to my heroku app, and I received the
> following error:
>
> "The memcache add-on has been disabled. Please choose an alternative service
> at https://addons.heroku.com/#caching";
>
> I don't see any information o
Hello,
I am attempting to add memcache to my heroku app, and I received the
following error:
"The memcache add-on has been disabled. Please choose an alternative
service at https://addons.heroku.com/#caching";
I don't see any information on the heroku site about this change, nor are
there any
