From: Dave Cramer <pg@fastcrypt.com>
To: Edoardo Ceccarelli <eddy@axa.it>
Cc: pgsql-jdbc@postgresql.org <pgsql-jdbc@postgresql.org>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: [JDBC] is a good practice to create an index on the oid?
Date: Mon, 26 Apr 2004 19:04:07 -0400
Message-ID: <1083020647.13952.164.camel@localhost.localdomain> (raw)
In-Reply-To: <408D3AE8.5020006@axa.it>
References: <408D3AE8.5020006@axa.it>
Yes, you can create an index on the oid, but unless you are selecting on
it, it is of little use.
you would have to do select * from foo where oid=? to get any value out
of the index.
Dave
On Mon, 2004-04-26 at 12:38, Edoardo Ceccarelli wrote:
> I am using the oid of the table as the main key and I've found that is
> not indexed (maybe because I have declared another primary key in the table)
>
> it is a good practice to create an index like this on the oid of a table?
> CREATE INDEX idoid annuncio400 USING btree (oid);
>
>
> does it work as a normal index?
>
> Thank you
> Edoardo
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
>
> !DSPAM:408d7c38183971270217895!
>
>
--
Dave Cramer
519 939 0336
ICQ # 14675561
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: pg@fastcrypt.com, eddy@axa.it, pgsql-jdbc@postgresql.org, pgsql-admin@postgresql.org
Subject: Re: [JDBC] is a good practice to create an index on the oid?
In-Reply-To: <1083020647.13952.164.camel@localhost.localdomain>
* 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