From: | "Lipker, Joseph" <Joseph(dot)Lipker(at)WRECO1(dot)com> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Migration \ OID question |
Date: | 2008-12-19 20:07:50 |
Message-ID: | C10317901E94094383071D851A6272E3038A9E147F@WAFEDIXMCMS14.corp.weyer.pri |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Have a question concerning how OID's are generated and assigned to tables in postgres.
The application I inherited relies upon the oid's for primary keys.
I am currently in process of migrating our current Postgres Database from one server [Postgres version 7.2] to another server [version 8.1.9]
PostgreSQL software was installed off the Linux 5 enterprise CD by our server team.
I have been able to perform and pgdump -o of the 7.2 database and restore to the 8.1.9 server without any errors.
However, I have noticed that the oids being generated and assigned when adding new records appear to have restarted from 17901. The current oid assigned from version 7.2 was 203199999.
The question is, after reloading the 7.2 version into the 8.19 version, should the migrated database be starting with the 203199999 as last oid and then assign 203200000 as the next oid?
What it is appears to be doing is restarting from beginning.
What I am concerned about is when the 8.1.9 version assigns an oid that already exists.
Any help on why this is happening would be appreciated.
Thanks,
Joe
Joseph Lipker
Weyerhaeuser Real Estate Company - IT Department
EC3-3C8
Federal Way, WA 98063-9777
Office: 253-924-5994
Cell: 253-249-6819
joseph(dot)lipker(at)wreco1(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-12-20 04:02:16 | Re: Migration \ OID question |
Previous Message | Mark Steben | 2008-12-19 18:09:16 | Re: Warm Standby - log shipping |