From: Tom Lane <tgl@sss.pgh.pa.us>
To: Decibel! <decibel@decibel.org>
Cc: Gurjeet Singh <singh.gurjeet@gmail.com>
Cc: \" \" Rodrigo E. De León Plicet \" \" <rdeleonp@gmail.com>
Cc: Madison Kelly <linux@alteeve.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Optimizing a VIEW
Date: Wed, 20 Aug 2008 14:18:33 -0400
Message-ID: <3072.1219256313@sss.pgh.pa.us> (raw)
In-Reply-To: <7FB7A77A-1F0B-4212-821F-06364A106A2B@decibel.org>
References: <48A5CCA4.2040206@alteeve.com>
<a55915760808161836k3f7e9d46ga8e5e99cf444a05f@mail.gmail.com>
<65937bea0808161919t4b0f19a0md90eae487b86429@mail.gmail.com>
<7FB7A77A-1F0B-4212-821F-06364A106A2B@decibel.org>
Decibel! <decibel@decibel.org> writes:
> On Aug 16, 2008, at 9:19 PM, Gurjeet Singh wrote:
>> Awesome!!!! Any comments on the performance of hstore?
> I've looked at it but haven't actually used it. One thing I wish it
> did was to keep a catalog somewhere of the "names" that it's seen so
> that it wasn't storing them as in-line text. If you have even
> moderate-length names and are storing small values you quickly end up
> wasting a ton of space.
> BTW, now that you can build arrays of composite types, that might be
> an easy way to deal with this stuff. Create a composite type of
> (name_id, value) and store that in an array.
If you're worried about storage space, I wouldn't go for arrays of
composite :-(. The tuple header overhead is horrendous, almost
certainly a lot worse than hstore.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, decibel@decibel.org, singh.gurjeet@gmail.com, rdeleonp@gmail.com, linux@alteeve.com
Subject: Re: Optimizing a VIEW
In-Reply-To: <3072.1219256313@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox