From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lipker, Joseph <Joseph.Lipker@WRECO1.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Migration \ OID question
Date: Fri, 19 Dec 2008 23:02:16 -0500
Message-ID: <9562.1229745736@sss.pgh.pa.us> (raw)
In-Reply-To: <C10317901E94094383071D851A6272E3038A9E147F@WAFEDIXMCMS14.corp.weyer.pri>
References: <C10317901E94094383071D851A6272E3038A9E147F@WAFEDIXMCMS14.corp.weyer.pri>
"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 the 203199999 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 will avoid assigning
duplicate OIDs. There might be some performance glitches if you have
very long runs of consecutive OIDs in the same table, though.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, Joseph.Lipker@WRECO1.com
Subject: Re: Migration \ OID question
In-Reply-To: <9562.1229745736@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox