Received: from rage.hub.org (root@nat194.17.mpoweredpc.net [142.177.194.17]) by hub.org (8.10.1/8.10.1) with ESMTP id e94Bi6G51855 for ; Wed, 4 Oct 2000 07:44:06 -0400 (EDT) Received: from localhost (bignose@localhost) by rage.hub.org (8.9.3/8.9.3) with ESMTP id IAA45718; Wed, 4 Oct 2000 08:43:46 -0300 (ADT) (envelope-from jeff@pgsql.com) X-Authentication-Warning: rage.hub.org: bignose owned process doing -bs Date: Wed, 4 Oct 2000 08:43:46 -0300 (ADT) From: Jeff MacDonald X-Sender: bignose@rage.hub.org Reply-To: Jeff MacDonald To: Josh Berkus cc: sqllist , Jeff MacDonald Subject: Re: OID Perfomance - Object-Relational databases In-Reply-To: <39DA03EA.7A1027E8@agliodbs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200010/53 Hi Josh, I didn't get right tho this, because well.. you asked the list, i figured i'd give them a chance first. and they've answered the same as i would have.. > Because it's a very elegant solution to my database structure issues, > I'm using OID's extensively as referents and foriegn keys. However, I > wanted to see if others had previous experience in this (answer as many > as you like): > > 1. Is there a performance loss on searches and joins when I use the OID > as a liniking field as opposed to a SERIAL column? yes, because indexes are automatcally created on serials. > 2. Can I define my own index on the OIDs of a table? sure, create index oid_idx on table(oid); Jeff MacDonald, ----------------------------------------------------- PostgreSQL Inc | Hub.Org Networking Services jeff@pgsql.com | jeff@hub.org www.pgsql.com | www.hub.org 1-902-542-0713 | 1-902-542-3657 ----------------------------------------------------- Facsimile : 1 902 542 5386 IRC Nick : bignose