Thanks Tom.
Unfortunately, none of the tables oid column have a unique index on them at this time. Will add them to adjust for
this.
You mentioned "performance glitches". What would those be? Errors or system performance slowdowns.
Joseph Lipker
>Weyerhaeuser Real Estate Company - IT Department
>EC3-3C8
>Federal Way, WA 98063-9777
>Office: 253-924-5994
Cell: 253-249-6819
joseph.lipker@wreco1.com
>
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, December 19, 2008 8:02 PM
To: Lipker, Joseph
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Migration \ OID question
"Lipker, Joseph" <Joseph.Lipker@WRECO1.com> writes:
> The application I inherited relies upon the oid's for primary keys.
It'd be a good idea to move away from that.
> The question is, after reloading the 7.2 version into the 8.19 version, should the migrated database be starting with
the203199999 as last oid and then assign 203200000 as the next oid?
No.
> What I am concerned about is when the 8.1.9 version assigns an oid that already exists.
If you have a unique index on the table's OID column (as one would hope, else it's not good for much) then 8.1 and up
willavoid assigning duplicate OIDs. There might be some performance glitches if you have very long runs of consecutive
OIDsin the same table, though.
regards, tom lane
