Re: hstore - Implementation and performance issues around its operators

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jul 19, 2011 at 5:06 PM, Stefan Keller <sfkeller@xxxxxxxxx> wrote:
> 2011/7/19 Robert Haas <robertmhaas@xxxxxxxxx>:
>> 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

-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux