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: Edoardo Ceccarelli <eddy(at)axa(dot)it>
Cc: pg(at)fastcrypt(dot)com,"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-28 08:25:26
Message-ID: 408F6A76.9070908@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-jdbcpgsql-performance
> 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


In response to

pgsql-performance by date

Next:From: Bruno Wolff IIIDate: 2004-04-28 08:32:23
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Previous:From: Manfred KoizarDate: 2004-04-28 08:24:41
Subject: Re: Simply join in PostrgeSQL takes too long

pgsql-admin by date

Next:From: Bruno Wolff IIIDate: 2004-04-28 08:32:23
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Previous:From: Edoardo CeccarelliDate: 2004-04-28 08:13:14
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the

pgsql-jdbc by date

Next:From: Bruno Wolff IIIDate: 2004-04-28 08:32:23
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Previous:From: Edoardo CeccarelliDate: 2004-04-28 08:13:14
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