Re: About OIDs - Mailing list pgsql-general

From Flower Sun
Subject Re: About OIDs
Date
Msg-id 20030328171243.81602.qmail@web14606.mail.yahoo.com
Whole thread Raw
In response to Re: About OIDs  ("Dann Corbit" <DCorbit@connx.com>)
List pgsql-general

Hi, Dann,

Do you think every database within a postgresql server has its own 32bits OID to use?

Thank you

 Dann Corbit <DCorbit@connx.com> wrote:

> -----Original Message-----
> From: Martijn van Oosterhout [mailto:kleptog@svana.org]
> Sent: Thursday, March 27, 2003 5:39 PM
> To: Dann Corbit
> Cc: Pgsql Group
> Subject: Re: [GENERAL] About OIDs
>
>
> On Thu, Mar 27, 2003 at 01:44:06PM -0800, Dann Corbit wrote:
> > They are very handy for our ODBC driver. It ensures that there is
> > always some sort of unique identifier for any table, even if the
> > designer did not create a primary key. (Sure, that's a
> naughty no-no,
> > but it is astonishing how often it happens). At any rate, some
> > complex joins can be sped up enormously by the existence of Odes.
>
> OIDs are not necessarily unique. How do you handle that?

I do assume that they are unique within a single table's Oid set.
However, I create a uni que index on the Oid column, so even when the
counter does wrap, I get a failure and an error message (yes, it has
happened).

When the failure does occur, I am forced to drop the database and
rebuild it. I will have a better solution once the 7.x official win32
port becomes available. God willing and the crick don't rise.


---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org



Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!

pgsql-general by date:

Previous
From: DeJuan Jackson
Date:
Subject: System lockup
Next
From: "scott.marlowe"
Date:
Subject: Re: missing FROM-clause notice but nothing is missing ...