pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Cramer <pg@fastcrypt.com>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Edoardo Ceccarelli <eddy@axa.it>
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 11:18:34 -0400
Message-ID: <1083079114.14759.204.camel@localhost.localdomain> (raw)
In-Reply-To: <408E75C2.5060703@familyhealth.com.au>
References: <408D3AE8.5020006@axa.it>
	<408DC9E1.8020704@familyhealth.com.au>
	<1083067187.14759.178.camel@localhost.localdomain>
	<408E75C2.5060703@familyhealth.com.au>

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!
> 
> 
-- 
Dave Cramer
519 939 0336
ICQ # 14675561




view thread (11+ messages)  latest in thread

Message-ID: <1083079114.14759.204.camel@localhost.localdomain>
Permalink:  ../1083079114.14759.204.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1083079114.14759.204.camel@localhost.localdomain

 · 

reply

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: pg@fastcrypt.com, chriskl@familyhealth.com.au, eddy@axa.it, 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: <1083079114.14759.204.camel@localhost.localdomain>

* 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