Re: Optimizing a VIEW - Mailing list pgsql-performance

From Tom Lane
Subject Re: Optimizing a VIEW
Date
Msg-id 3072.1219256313@sss.pgh.pa.us
Whole thread Raw
In response to Re: Optimizing a VIEW  (Decibel! <decibel@decibel.org>)
Responses Re: Optimizing a VIEW
List pgsql-performance
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

pgsql-performance by date:

Previous
From: "Scott Carey"
Date:
Subject: Re: Slow query with a lot of data
Next
From: Tom Lane
Date:
Subject: Re: Slow query with a lot of data