Re: hstore improvements?
| От | Andrew Gierth |
|---|---|
| Тема | Re: hstore improvements? |
| Дата | |
| Msg-id | 87eiws2bfh.fsf@news-spur.riddles.org.uk обсуждение исходный текст |
| Ответ на | Re: hstore improvements? (Josh Berkus <josh@agliodbs.com>) |
| Список | pgsql-hackers |
>>>>> "Josh" == Josh Berkus <josh@agliodbs.com> writes: > Tom Lane wrote:>> Josh Berkus <josh@agliodbs.com> writes:>>> As an hstore user, I'd be fine with simply limiting it to64K (or,>>> heck, 8K) and throwing an error. I'd also be fine with limiting>>> keys to 255 bytes, although we'd have towarn people.>> Yeah, 255 might well be more of a problem than the other limit. We>> could move to something like 10/22or 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 useJosh> hstore more heavily than most people, and that if thelimitsJosh> 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 anJosh> object store, so you'll make them happy with a new footgun.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.
В списке pgsql-hackers по дате отправления: