Table Creation Question.

From: <postgres(at)athena(dot)frontlogic(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Table Creation Question.
Date: 2001-04-25 16:48:31
Message-ID: 9c6v4u$2bpv$1@news.tht.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello, I'm wondering if anyone could point me towards performance/space
tradeoffs for large tables in Postgres. I would like to create a very
large table that has in each tuple a varchar and a list of integers. What
are the benefits of designing my table as a varchar/array of integers
vs. the more standard relational way of having a separate tuple for each
varchar/integer pair?

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.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-04-25 16:50:48 Re: Newbie struggling to set $PGDATA
Previous Message Lieven Van Acker 2001-04-25 16:46:37 Re: Joined table view - multiple delete action rule