From: Edoardo Ceccarelli <eddy@axa.it>
To: pg@fastcrypt.com
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-jdbc@postgresql.org <pgsql-jdbc@postgresql.org>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Date: Tue, 27 Apr 2004 23:42:58 +0200
Message-ID: <408ED3E2.802@axa.it> (raw)
In-Reply-To: <1083079114.14759.204.camel@localhost.localdomain>
References: <408D3AE8.5020006@axa.it>
<408DC9E1.8020704@familyhealth.com.au>
<1083067187.14759.178.camel@localhost.localdomain>
<408E75C2.5060703@familyhealth.com.au>
<1083079114.14759.204.camel@localhost.localdomain>
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!
>>
>>
>>
>>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: eddy@axa.it, pg@fastcrypt.com, chriskl@familyhealth.com.au, pgsql-jdbc@postgresql.org, pgsql-admin@postgresql.org
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
In-Reply-To: <408ED3E2.802@axa.it>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox