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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-jdbc pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Edoardo Ceccarelli | 2004-04-28 08:13:14 | Re: [JDBC] [PERFORM] is a good practice to create an index on the |
Previous Message | Jim Seymour | 2004-04-27 21:50:03 | Re: Recover data |
From | Date | Subject | |
---|---|---|---|
Next Message | Edoardo Ceccarelli | 2004-04-28 08:13:14 | Re: [JDBC] [PERFORM] is a good practice to create an index on the |
Previous Message | Edoardo Ceccarelli | 2004-04-27 21:42:58 | Re: [JDBC] [PERFORM] is a good practice to create an index on the |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-04-28 04:27:59 | Re: planner/optimizer question |
Previous Message | Josh Berkus | 2004-04-27 22:37:09 | Re: Simply join in PostrgeSQL takes too long |