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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-jdbc pgsql-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

Browse pgsql-admin by date

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

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2004-04-27 15:18:34 Re: [JDBC] [PERFORM] is a good practice to create an index on the
Previous Message Dave Cramer 2004-04-27 11:59:47 Re: [JDBC] [PERFORM] is a good practice to create an index on the

Browse pgsql-performance by date

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