Michael Fork <[EMAIL PROTECTED]> writes: > Just a thought, but couldn't you create a sequence that is referenced by > multiple tables, I was going to suggest exactly that. It's not quite as simple as a "serial" column declaration, but you can split the use of an ID sequence generator over just as many tables as you need to have unique IDs across. That way you don't have a problem at dump/reload time, and you don't exhaust your ID space any faster than you must. regards, tom lane
- [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
- Re: [SQL] OID Perfomance - Object-Relational datab... Mitch Vincent
- RE: [SQL] OID Perfomance - Object-Relational databases Michael Ansley
- RE: [SQL] OID Perfomance - Object-Relational databases Michael Ansley
- RE: [SQL] OID Perfomance - Object-Relational databases Michael Ansley
- Re: [SQL] OID Perfomance - Object-Relational databases Josh Berkus