Re: hstore - Implementation and performance issues around its operators - Mailing list pgsql-performance

From Robert Haas
Subject Re: hstore - Implementation and performance issues around its operators
Date
Msg-id CA+Tgmoac3JQHYD5uTPmdrR7fgweE3D+cddOuEo4-VGQjtEmO5g@mail.gmail.com
Whole thread Raw
In response to Re: hstore - Implementation and performance issues around its operators  (Stefan Keller <sfkeller@gmail.com>)
List pgsql-performance
On Tue, Jul 19, 2011 at 5:06 PM, Stefan Keller <sfkeller@gmail.com> wrote:
> 2011/7/19 Robert Haas <robertmhaas@gmail.com>:
>> Putting the elements in order wouldn't really help, would it?  I mean,
>> you'd need some kind of an index inside the hstore... which there
>> isn't.
>
> Sorry for my inprecise question. In fact elements of a hstore are
> stored in order of (keylength,key) with the key comparison done
> bytewise (not locale-dependent). See e.g. function hstoreUniquePairs
> in http://doxygen.postgresql.org/ . This ordered property is being
> used by some hstore functions but not all - and I'm still wondering
> why.

Not sure, honestly.  Is there some place where it would permit an
optimization we're not currently doing?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-performance by date:

Previous
From: Jose Ildefonso Camargo Tolosa
Date:
Subject: Re: Large rows number, and large objects
Next
From: Дмитрий Васильев
Date:
Subject: Bad query plan