Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id 2877C194E782
	for <pgsql-admin@postgresql.org>; Wed,  6 Jun 2012 18:04:05 -0300 (ADT)
Received: from mail03.insiderscore.com ([207.10.33.141])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ralbright@insiderscore.com>) id 1ScNOe-0003fc-DH
	for pgsql-admin@postgresql.org; Wed, 06 Jun 2012 21:04:05 +0000
Received: from [192.168.0.100] (pool-71-245-122-212.cmdnnj.fios.verizon.net
	[71.245.122.212])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail03.insiderscore.com (Postfix) with ESMTP id 4088120A6C1
	for <pgsql-admin@postgresql.org>; Wed,  6 Jun 2012 17:03:51 -0400 (EDT)
X-DomainKeys: Sendmail DomainKeys Filter v1.0.1 mail03.insiderscore.com
	4088120A6C1
DomainKey-Signature: a=rsa-sha1; s=is; d=insiderscore.com; c=simple; q=dns;
	b=XXqJlEuvBjA5KEkvvHF+eKhnQmYN3qPavNpKleAed1P8GYFsHiD3eM5/jts9gcjzF
	rNhczLNU+V5mMJIw8vRP9nakkVN8wXZv4ocC1dYpuYiwTJQb9xXPFjGpIdOWdhq
Message-ID: <4FCFC5B6.1070300@insiderscore.com>
Date: Wed, 06 Jun 2012 17:03:50 -0400
From: Richard Albright <ralbright@insiderscore.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Re: Hstore vs simple K:V
References: <1339014818.64273.YahooMailNeo@web161505.mail.bf1.yahoo.com>
In-Reply-To: <1339014818.64273.YahooMailNeo@web161505.mail.bf1.yahoo.com>
Content-Type: multipart/alternative;
	boundary="------------030507080204080400090005"
X-Pg-Spam-Score: -5.5 (-----)
X-Archive-Number: 201206/19
X-Sequence-Number: 39610

This is a multi-part message in MIME format.
--------------030507080204080400090005
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

You don't need to do an entity attribute value model in a separate table 
to include mutliple key value pairs. since an hstore is schemaless, you 
can include them all in one column for a particular row.

On 06/06/2012 04:33 PM, A J wrote:
> What are the key benefits of using hstore over simple K:V storage in 
> Postgres where you split the key in its own column and value in its 
> own column ?
>
> Thank you for any inputs.


-- 
*Rick Albright*
Senior Quantitative Analyst
Web: www.insiderscore.com <https://www.insiderscore.com/>
Email: ralbright@insiderscore.com <mailto:ralbright@insiderscore.com>

--------------030507080204080400090005
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    You don't need to do an entity attribute value model in a separate
    table to include mutliple key value pairs. since an hstore is
    schemaless, you can include them all in one column for a particular
    row.<br>
    <br>
    On 06/06/2012 04:33 PM, A J wrote:
    <blockquote
      cite="mid:1339014818.64273.YahooMailNeo@web161505.mail.bf1.yahoo.com"
      type="cite">
      <div style="color:#000; background-color:#fff; font-family:times
        new roman, new york, times, serif;font-size:12pt">
        <div>What are the key benefits of using hstore over simple K:V
          storage in Postgres where you split the key in its own column
          and value in its own column ?</div>
        <div><br>
          Thank you for any inputs.<br>
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <b>Rick Albright</b>
      <br>
      Senior Quantitative Analyst
      <br>
      Web: <a href="https://www.insiderscore.com/">www.insiderscore.com</a>
      <br>
      Email: <a href="mailto:ralbright@insiderscore.com">ralbright@insiderscore.com</a>
    </div>
  </body>
</html>

--------------030507080204080400090005--