Re: Impact of loss of unique SERIAL?

From: Hacksaw <hacksaw(at)hacksaw(dot)org>
To: Andrew Sullivan <andrew(at)libertyrms(dot)info>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Impact of loss of unique SERIAL?
Date: 2003-05-01 23:35:15
Message-ID: 200305012335.h41NZF2J022516@habitrail.home.fools-errant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> From: Andrew Sullivan <andrew(at)libertyrms(dot)info>
> I don't actually recall the argument for removing the automatic
> unique index. But it's easy enough at the time of creation, since
> you could specify a UNIQUE constraint on the column anyway.

Well, I've no idea what the PostgreSQL's particular argument might have been,
but too many indices typically means slower lookups. You want the indices to
be created based on the fields you will most often mention in WHERE statements.

A unique serial number is always useful, but might not be looked at unless the
the final output is a surprising number of records, like two, where one is
expected. No point in indexing it then.

--
Music is a quality, organised in sound and in time.
http://www.hacksaw.org -- http://www.privatecircus.com -- KB1FVD

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Andrei Verovski (aka MacGuru) 2003-05-02 08:51:25 Changing colums type
Previous Message Lamar Owen 2003-05-01 22:38:53 Re: RH 9 upgrade