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 B3898D1B445; Wed, 28 Apr 2004 05:19:44 -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 43428-01; Wed, 28 Apr 2004 05:19:43 -0300 (ADT) Received: from houston.familyhealth.com.au (fhnet.arach.net.au [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id 59FEBD1B478; Wed, 28 Apr 2004 05:19:40 -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 i3S8JTWL045110; Wed, 28 Apr 2004 16:19:29 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Message-ID: <408F6A76.9070908@familyhealth.com.au> Date: Wed, 28 Apr 2004 16:25:26 +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> <408F0944.5060608@familyhealth.com.au> <408F679A.9030608@axa.it> In-Reply-To: <408F679A.9030608@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/331 X-Sequence-Number: 13304 > do you mean that, declaring an index serial, I'd never have to deal with > incrementing its primary key? good to know! Yep. You can use 'DEFAULT' as the value, eg: INSERT INTO blah (DEFAULT, ...); > 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 :) Sure. Chris