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 ABBFCD1B8D1; Wed, 28 Apr 2004 05:13:51 -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 40407-07; Wed, 28 Apr 2004 05:13:49 -0300 (ADT) Received: from FE-mail04.sfg.albacom.net (FE-mail04.albacom.net [213.217.149.84]) by svr1.postgresql.org (Postfix) with ESMTP id CC622D1B8EF; Wed, 28 Apr 2004 05:13:47 -0300 (ADT) Received: from axa.it (217.221.80.72) by FE-mail04.sfg.albacom.net (7.0.009) id 408E270C0002A496; Wed, 28 Apr 2004 10:13:12 +0200 Message-ID: <408F679A.9030608@axa.it> Date: Wed, 28 Apr 2004 10:13:14 +0200 From: Edoardo Ceccarelli User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: it, en, en-us MIME-Version: 1.0 To: Christopher Kings-Lynne 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> <408F0944.5060608@familyhealth.com.au> In-Reply-To: <408F0944.5060608@familyhealth.com.au> Content-Type: text/plain; charset=ISO-8859-1; 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/330 X-Sequence-Number: 13303 do you mean that, declaring an index serial, I'd never have to deal with incrementing its primary key? good to know! anyway in this particular situation I don't need such accurate behaviour: this table is filled up with a lot of data twice per week and it's used only to answer queries. I could drop it whenever I want :) Thanks again, eddy Christopher Kings-Lynne ha scritto: >> 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 > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > > >