Search Postgresql Archives

Re: Composite types as columns used in production?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



James Robinson <jlrobins@xxxxxxxxxxxxxxx> 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

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux