Re: hstore improvements?

>>>>> "Josh" == Josh Berkus <josh(at)agliodbs(dot)com> writes:

> Tom Lane wrote:
>> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>>> As an hstore user, I'd be fine with simply limiting it to 64K (or,
>>> heck, 8K) and throwing an error. I'd also be fine with limiting
>>> keys to 255 bytes, although we'd have to warn people.
>> Yeah, 255 might well be more of a problem than the other limit. We
>> could move to something like 10/22 or 12/20 split, which would give
>> us 1KB/4MB or 4KB/1MB limits.

Josh> Anything you like. What I'm saying is that I think I use
Josh> hstore more heavily than most people, and that if the limits
Josh> were as low as 255b/8K it wouldn't hurt me any.

Josh> I suppose 1K/4MB would allow OO-types to use hstore as an
Josh> object store, so you'll make them happy with a new foot gun.
Josh> Why not?

I decided to obviate the entire question and remove the limits
altogether (while still keeping the overhead the same, i.e. 8 bytes
per entry).

--
Andrew.