Re: primary key and existing unique fields

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Sally Sally <dedeb17(at)hotmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, qnex42(at)gmail(dot)com
Subject: Re: primary key and existing unique fields
Date: 2004-10-28 17:44:00
Message-ID: 20041028174400.GC12318@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 28, 2004 at 14:31:32 +0000,
Sally Sally <dedeb17(at)hotmail(dot)com> wrote:
> Dawid,
> I am interested in the first point you made that:
> having varchar(12) in every referencing table, takes more storage
> space.
> The thing is though, if I have a serial primary key then it would be an
> additional column. Or you are saying the space taken by a VARCHAR(12) field
> is more than two INT fields? ( or is it the fact that when it is referenced
> it will appear several times?) I guess the reason I am resisting the idea
> of an additional primary key field is to avoid the additional lookup in
> some queries. Perhaps it's a minor almost irrelevant performance factor.

I think it is better to worry about what is going to make it easiest to
have clean data and to support future changes than worry about performance.
Over the long run hardware is cheaper than people.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Hallgren 2004-10-28 19:07:28 Re: Reasoning behind process instead of thread based
Previous Message Robby Russell 2004-10-28 17:42:19 Re: determine sequence name for a serial