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?
- [SQL] OID Perfomance - Object-Relational databases Josh Berkus
- Re: [SQL] OID Perfomance - another question Mitch Vincent
- Re: [SQL] OID Perfomance - another question Tod McQuillin
- Re: [SQL] OID Perfomance - Object-Relational databases Tom Lane
- Re: [SQL] OID Perfomance - Object-Relational datab... Josh Berkus
- Re: [SQL] OID Perfomance - Object-Relational d... Michael Fork
- Re: [SQL] OID Perfomance - Object-Relational d... Tom Lane
- Re: [SQL] OID Perfomance - Object-Relation... Josh Berkus
- Re: [SQL] OID Perfomance - Object-Rel... Bruce Momjian
- [SQL] Re: OID Perfomance - Object-Relational databases Jeff MacDonald
- RE: [SQL] OID Perfomance - Object-Relational databases Michael Ansley