X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 17793D1B498; Tue, 27 Apr 2004 22:25:13 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 06476-06; Tue, 27 Apr 2004 22:25:13 -0300 (ADT) Received: from houston.familyhealth.com.au (fhnet.arach.net.au [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id 005F4D1C942; Tue, 27 Apr 2004 22:25:08 -0300 (ADT) Received: from familyhealth.com.au (work-40.internal [192.168.0.40]) by houston.familyhealth.com.au (8.12.9p1/8.12.9) with ESMTP id i3S1OxWL006768; Wed, 28 Apr 2004 09:24:59 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Message-ID: <408F0944.5060608@familyhealth.com.au> Date: Wed, 28 Apr 2004 09:30:44 +0800 From: Christopher Kings-Lynne User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Edoardo Ceccarelli Cc: pg@fastcrypt.com, "pgsql-jdbc@postgresql.org" , pgsql-performance@postgresql.org, pgsql-admin@postgresql.org Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the 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> <408ED3E2.802@axa.it> In-Reply-To: <408ED3E2.802@axa.it> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=3.0 tagged_above=0.0 required=5.0 tests=SUSPICIOUS_RECIPS X-Spam-Level: *** X-Archive-Number: 200404/329 X-Sequence-Number: 13302 > I am going to use them as primary key of the table, so I'll surely need > them unique :) Eduoardo, I REALLY suggest you don't use them at all. You should make a primary key like this: CREATE TABLE blah ( id SERIAL PRIMARY KEY, ... ); Also note that by default, OIDs are NOT dumped by pg_dump. You will need to add extra switches to your pg_dump backup to ensure that they are. Chris