| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-jdbc pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2004-04-28 08:32:23 | Re: [JDBC] [PERFORM] is a good practice to create an index on the |
| Previous Message | Edoardo Ceccarelli | 2004-04-28 08:13:14 | Re: [JDBC] [PERFORM] is a good practice to create an index on the |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2004-04-28 08:32:23 | Re: [JDBC] [PERFORM] is a good practice to create an index on the |
| Previous Message | Edoardo Ceccarelli | 2004-04-28 08:13:14 | Re: [JDBC] [PERFORM] is a good practice to create an index on the |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2004-04-28 08:32:23 | Re: [JDBC] [PERFORM] is a good practice to create an index on the |
| Previous Message | Manfred Koizar | 2004-04-28 08:24:41 | Re: Simply join in PostrgeSQL takes too long |