hstore improvements?

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: pgsql-hackers(at)postgresql(dot)org
Subject: hstore improvements?
Date: 2009-03-13 18:06:26
Message-ID: 87hc1xi9gd.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

I have a patch almost done that adds some obvious but currently
missing functionality to hstore, specifically the ability to construct
an hstore from a record, and the ability to construct one from a pair
of arrays.

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

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?

Andrew (irc:RhodiumToad)


Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-03-13 18:34:30 Re: hstore improvements?
Previous Message Tom Lane 2009-03-13 17:18:22 Re: Out parameters handling