I am running a somewhat unfamiliar Ruby automation results app using
ActiveRecord to manage the postgres 9.0 backend. During our automation runs we
sometimes get bursts of HTTP 500 errors coming back at us, and the Ruby app log
shows an Hstore::TooBig error:
Hstore::TooBig (Hstore::TooBig):
On Oct 31, 2013, at 3:46 PM, john gale j...@smadness.com wrote:
I don't quite know where this error is coming from. The ActiveRecord source
doesn't seem to have it, and I'm not familiar enough with Rails or
ActiveRecord to track definitively whether the failing function is actually
On 10/31/2013 03:46 PM, john gale wrote:
I am running a somewhat unfamiliar Ruby automation results app using
ActiveRecord to manage the postgres 9.0 backend. During our automation runs we
sometimes get bursts of HTTP 500 errors coming back at us, and the Ruby app log
shows an
On Oct 31, 2013, at 4:44 PM, Adrian Klaver adrian.kla...@gmail.com wrote:
So to piece out the questions,
- is there a total size limitation of the hstore field? or is it
theoretically large enough (1GB) that it really shouldn't matter?
- is there a string size limitation of each key/val in
On Oct 31, 2013, at 4:44 PM, Adrian Klaver adrian.kla...@gmail.com wrote:
So to piece out the questions,
- is there a total size limitation of the hstore field? or is it
theoretically large enough (1GB) that it really shouldn't matter?
- is there a string size limitation of each key/val in
On 10/31/2013 5:11 PM, john gale wrote:
The further questions still apply though; are there documented size
limitations for hstore?
afaik only the practical limits of how big you want your tables to get,
and the 1GB limit of the underlying text representation. having many
1000s of keys in
