| From: | Edoardo Ceccarelli <eddy(at)axa(dot)it> |
|---|---|
| To: | pg(at)fastcrypt(dot)com |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, "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-27 21:42:58 |
| Message-ID: | 408ED3E2.802@axa.it |
| 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 :)
thank you for you help
Edoardo
Dave Cramer ha scritto:
>Edoardo,
>
>Are you using them for referential integrity? If so you would be wise to
>use sequences instead.
>
>Christopher: yes you are correct, I wasn't sure if that is what he was
>doing.
>
>Dave
>On Tue, 2004-04-27 at 11:01, Christopher Kings-Lynne wrote:
>
>
>>>AFAIK, oids aren't used for anything internally, so duplicates don't
>>>really matter. Besides, what would you do about duplicate oid's ?
>>>
>>>
>>If he's using them _externally_, then he does have to worry about
>>duplicates.
>>
>>Chris
>>
>>
>>
>>!DSPAM:408e75e0137721921318500!
>>
>>
>>
>>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Seymour | 2004-04-27 21:50:03 | Re: Recover data |
| Previous Message | Eduardo Naschenweng | 2004-04-27 20:21:31 | Optimizer choosing smaller index instead of right one |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-04-28 01:30:44 | Re: [JDBC] [PERFORM] is a good practice to create an index on the |
| Previous Message | Kris Jurka | 2004-04-27 19:05:47 | Re: setCatalog |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atesz | 2004-04-27 21:56:07 | Re: Simply join in PostrgeSQL takes too long |
| Previous Message | Vitaly Belman | 2004-04-27 21:27:40 | Simply join in PostrgeSQL takes too long |