Re: hstore improvements?

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: hstore improvements?
Date: 2009-03-13 19:34:50
Message-ID: 1821EEB2-1B30-43A7-9D57-3BB4DFAE08AA@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mar 13, 2009, at 11:06 AM, Andrew Gierth wrote:

> If there's any other features that people find notably missing from
> hstore, I could stick them in too; any requests?

Can you create slices? That is, create a new hstore as a subset of an
existing hstore?

> Also, hstore has an (undocumented) limit of 65535 bytes for keys and
> values, and it does not behave very cleanly when given longer values
> (it truncates them mod 2^16, rather than erroring). That gives rise to
> two obvious questions: (1) are those lengths reasonable? they strike
> me as being rather long for keys and rather short for values; and (2)
> should exceeding the lengths throw an error?

I agree. The keys can be much shorter without any threat of loss. Can
the value not essentially be TEXT, and thus theoretically unlimited in
size?

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-03-13 20:06:48 Re: hstore improvements?
Previous Message Alvaro Herrera 2009-03-13 19:16:33 Re: hstore improvements?