From: | Decibel! <decibel(at)decibel(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, "\" \" Rodrigo E(dot) De León Plicet \" \"" <rdeleonp(at)gmail(dot)com>, "Madison Kelly" <linux(at)alteeve(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Optimizing a VIEW |
Date: | 2008-08-22 04:53:58 |
Message-ID: | C1A872C5-5399-4139-A1E2-1A93142F2C69@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
From | Date | Subject | |
---|---|---|---|
Next Message | Kranti K K Parisa™ | 2008-08-22 05:52:16 | Re: PostgreSQL+Hibernate Performance |
Previous Message | Tom Lane | 2008-08-22 00:49:17 | Re: Why do my hash joins turn to nested loops? |