Message-ID: <38FAAA8E.A21C273F@hp.com>
Date: Mon, 17 Apr 2000 00:09:18 -0600
From: Ryan Bradetich <ryan_bradetich@hp.com>
MIME-Version: 1.0
To: Andrew Perrin - Demography <aperrin@demog.berkeley.edu>
Cc: pgsql-sql@postgresql.org
Subject: Re: indexes and keys
References: 
 <Pine.SUN.4.10.10004162158200.2584-100000@davis.DEMOG.Berkeley.EDU>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Andrew,

The one created should be sufficient.  You can check to make sure
it fits your needs exactly by: \d <index name>

Ryan

Andrew Perrin - Demography wrote:

> Greetings - I hope this is a simple question.
>
> Is there any reason to create an index on a column that already has one
> created as part of a SERIAL datatype?  That is, I used:
>
> CREATE TABLE personal_data (id serial ...);
>
> to create it, so \d shows:
>
>  | postgres         | personal_data                    | table    |
>  | postgres         | personal_data                    | table    |
>  | postgres         | personal_data_id_key             | index    |
>  | postgres         | personal_data_id_seq             | sequence |
>
> is there any reason to create another index on id:
>
> CREATE INDEX pd_id_idx on personal_data;
>
> or will the automatically created one be sufficient?
>
> Thanks.
>
> ---------------------------------------------------------------------
> Andrew J. Perrin - aperrin@demog.berkeley.edu - NT/Unix Admin/Support
> Department of Demography    -    University of California at Berkeley
> 2232 Piedmont Avenue #2120  -    Berkeley, California, 94720-2120 USA
> http://demog.berkeley.edu/~aperrin --------------------------SEIU1199

--
Ryan Bradetich
AIT Operations
Unix Platform Team