Re: Composite types as columns used in production?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: James Robinson <jlrobins(at)socialserve(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Composite types as columns used in production?
Date: 2005-04-29 17:23:53
Message-ID: 7094.1114795433@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

James Robinson <jlrobins(at)socialserve(dot)com> writes:
> That said -- anyone stepping up to claiming using 'em? Are these things
> seen as against the data normalization grain?

One strike against 'em is the fairly high overhead involved --- a
composite value is stored as effectively its own tuple, so there's 28 or
so bytes of overhead for each one.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-04-29 17:26:04 Re: Increasing statistics results in worse estimates
Previous Message Michael Fuhr 2005-04-29 17:21:35 Re: [GENERAL] Returning a RECORD, not SETOF RECORD