Re: Optimizing a VIEW - Mailing list pgsql-performance

From Decibel!
Subject Re: Optimizing a VIEW
Date
Msg-id C1A872C5-5399-4139-A1E2-1A93142F2C69@decibel.org
Whole thread Raw
In response to Re: Optimizing a VIEW  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On Aug 20, 2008, at 1:18 PM, Tom Lane wrote:
> 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.


Oh holy cow, I didn't realize we had a big header in there. Is that
to allow for changing the definition of the composite type?
--
Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828



Attachment

pgsql-performance by date:

Previous
From: Brad Ediger
Date:
Subject: Nested Loop join being improperly chosen
Next
From: André Volpato
Date:
Subject: Re: Postgres not using array