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

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

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Edoardo Ceccarelli <eddy(at)axa(dot)it>,"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 15:18:34
Message-ID: 1083079114.14759.204.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-jdbcpgsql-performance
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


In response to

Responses

pgsql-performance by date

Next:From: Silke TrisslDate: 2004-04-27 17:32:36
Subject: Join problem
Previous:From: Christopher Kings-LynneDate: 2004-04-27 15:01:22
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the

pgsql-admin by date

Next:From: Chris HooverDate: 2004-04-27 17:21:34
Subject: Breaking out log by database
Previous:From: Christopher Kings-LynneDate: 2004-04-27 15:01:22
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the

pgsql-jdbc by date

Next:From: Dave CramerDate: 2004-04-27 18:52:58
Subject: setCatalog
Previous:From: Christopher Kings-LynneDate: 2004-04-27 15:01:22
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