From: Edoardo Ceccarelli <eddy@axa.it>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pg@fastcrypt.com, "pgsql-jdbc@postgresql.org" <pgsql-jdbc@postgresql.org>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
Date: Wed, 28 Apr 2004 10:13:14 +0200
Message-ID: <408F679A.9030608@axa.it> (raw)
In-Reply-To: <408F0944.5060608@familyhealth.com.au>
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>
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
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: eddy@axa.it, chriskl@familyhealth.com.au, pgsql-jdbc@postgresql.org, pgsql-admin@postgresql.org
Subject: Re: [JDBC] [PERFORM] is a good practice to create an index on the
In-Reply-To: <408F679A.9030608@axa.it>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox