Hstore vs simple K:V
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Hstore vs simple K:V
From
: A J <
s5aly@xxxxxxxxx
>
Date
: Wed, 6 Jun 2012 13:33:38 -0700 (PDT)
Reply-to
: A J <
s5aly@xxxxxxxxx
>
Sender
:
pgsql-admin-owner@xxxxxxxxxxxxxx
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.
Follow-Ups
:
Re: Hstore vs simple K:V
From:
Richard Albright
Prev by Date:
Re: Data split -- Creating a copy of database without outage
Next by Date:
Re: Can schemas be ordered regarding their creation time ?
Previous by thread:
postgres block size alignment with filesystem block size
Next by thread:
Re: Hstore vs simple K:V
Index(es):
Date
Thread
[Index of Archives]
[KVM ARM]
[KVM ia64]
[KVM ppc]
[Virtualization Tools]
[Spice Development]
[Libvirt]
[Libvirt Users]
[Linux USB Devel]
[Linux Audio Users]
[Yosemite Questions]
[Linux Kernel]
[Linux SCSI]
[XFree86]
