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

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

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: pg(at)fastcrypt(dot)com
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:01:22
Message-ID: 408E75C2.5060703@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-jdbcpgsql-performance
> 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


In response to

Responses

pgsql-performance by date

Next:From: Dave CramerDate: 2004-04-27 15:18:34
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Previous:From: AteszDate: 2004-04-27 12:54:27
Subject: Re: planner/optimizer question

pgsql-admin by date

Next:From: Dave CramerDate: 2004-04-27 15:18:34
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Previous:From: Stephan SzaboDate: 2004-04-27 13:56:16
Subject: Re: delete cascade question

pgsql-jdbc by date

Next:From: Dave CramerDate: 2004-04-27 15:18:34
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Previous:From: Dave CramerDate: 2004-04-27 11:59:47
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