Re: KVP table vs. hstore - hstore performance (Was: Postgres NoSQL emulation)

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Stefan Keller <sfkeller(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: KVP table vs. hstore - hstore performance (Was: Postgres NoSQL emulation)
Date: 2011-05-16 13:47:09
Message-ID: BANLkTi=BuodrCmgrAE3_ydKukfLwSVzQrg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sat, May 14, 2011 at 5:10 AM, Stefan Keller <sfkeller(at)gmail(dot)com> wrote:
> Hi,
>
> I am conducting a benchmark to compare KVP table vs. hstore and got
> bad hstore performance results when the no. of records is greater than
> about 500'000.
>
> CREATE TABLE kvp ( id SERIAL PRIMARY KEY, key text NOT NULL, value text );
> -- with index on key
> CREATE TABLE myhstore ( id SERIAL PRIMARY KEY, obj hstore NOT NULL );
> -- with GIST index on obj
>
> Does anyone have experience with that?

hstore is not really designed for large-ish sets like that.

merlin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2011-05-16 14:15:59 Re: Why query takes soo much time
Previous Message John Rouillard 2011-05-16 13:17:30 Re: Using pgiosim realistically