From: | <postgres(at)athena(dot)frontlogic(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Table Creation Question. |
Date: | 2001-04-26 21:51:52 |
Message-ID: | 9ca59n$30cm$2@news.tht.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In comp.databases.postgresql.general Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> postgres(at)athena(dot)frontlogic(dot)com writes:
>> I assume using the array type would save me some cost on storage, while
>> using the varchar/integer pairs would result in faster queries. Is this
>> correct? Thanks for any help or pointers.
> As long as you don't want to look up or join against invidual array
> members, the array solution is going to be more space and time efficient.
Thanks for the reply. I am going to join on individual members, so I will shy away
from array types. I'm uncomfortable with array types in general, because of their
deviance from the relational model. Does anyone have any links to a discussion of
the pros and cons of using array types?
From | Date | Subject | |
---|---|---|---|
Next Message | John Coers | 2001-04-26 22:11:56 | Performance with Large Volumes of Data |
Previous Message | Thomas F. O'Connell | 2001-04-26 21:32:52 | creating constants in postgres |