Skip site navigation (1) Skip section navigation (2)

Re: [JDBC] [PERFORM] is a good practice to create an index on the

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Edoardo Ceccarelli <eddy(at)axa(dot)it>
Cc: pg(at)fastcrypt(dot)com,"pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>,pgsql-performance(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Date: 2004-04-28 01:30:44
Message-ID: 408F0944.5060608@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-jdbcpgsql-performance
> I am going to use them as primary key of the table, so I'll surely need 
> them unique :)

Eduoardo, I REALLY suggest you don't use them at all.  You should make a 
primary key like this:

CREATE TABLE blah (
   id SERIAL PRIMARY KEY,
   ...
);

Also note that by default, OIDs are NOT dumped by pg_dump.  You will 
need to add extra switches to your pg_dump backup to ensure that they are.

Chris


In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2004-04-28 04:27:59
Subject: Re: planner/optimizer question
Previous:From: Josh BerkusDate: 2004-04-27 22:37:09
Subject: Re: Simply join in PostrgeSQL takes too long

pgsql-admin by date

Next:From: Edoardo CeccarelliDate: 2004-04-28 08:13:14
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Previous:From: Jim SeymourDate: 2004-04-27 21:50:03
Subject: Re: Recover data

pgsql-jdbc by date

Next:From: Edoardo CeccarelliDate: 2004-04-28 08:13:14
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Previous:From: Edoardo CeccarelliDate: 2004-04-27 21:42:58
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group