Re: OID Perfomance - another question

From: "Mitch Vincent" <mitch(at)venux(dot)net>
To: <josh(at)agliodbs(dot)com>
Cc: "sqllist" <pgsql-sql(at)postgresql(dot)org>
Subject: Re: OID Perfomance - another question
Date: 2000-10-03 16:23:12
Message-ID: 00b701c02d56$3a301180$0200000a@doot
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Aren't there a pretty big concerns when using OIDs as IDs to relate records
in different tables to each other? Wouldn't the OIDs be totally re-assigned
if you had to dump/restore your database?

Just a question to satisfy my own curiosity, thanks!

-Mitch

> Folks,
>
> 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?

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tod McQuillin 2000-10-03 16:24:28 Re: OID Perfomance - another question
Previous Message Michael Ansley 2000-10-03 16:17:17 RE: OID Perfomance - Object-Relational databases