Re: OID Implicit limit

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Steve Howe <howe(at)carcass(dot)dhs(dot)org>, Pgsql-Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: OID Implicit limit
Date: 2000-12-20 02:49:12
Message-ID: 200012200249.VAA15154@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

We have an FAQ item on this now under OID's.

[ Charset ISO-8859-1 unsupported, converting... ]
> > > Reading the documentation, I see that OIDs are unique through
> the
> > > whole database.
> > > But since OIDs are int4, does that limit the number of rows I
> can
> > > have in a database to 2^32 = 4 billion ?
> >
> > Yep.
> >
> > Thanks for the answer - although that concerns me a bit.
> > Maybe I could recompile it setting oid to int64 type...
>
> If that really concerns you, then the rest of the hackers list I think would
> be very interested in hearing of a real-world database with more than 4
> billion rows/inserts/deletes.
>
> Apparently it is somewhat more complicated than just 'recompiling as an
> int64' to change this. I believe that patches are currently being made to
> facilitate a future move towards 64bit OIDs, but I am not certain of the
> status.
>
> Chris
>
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-12-20 03:03:15 Re: [HACKERS] Re: 7.1 features list
Previous Message Bruce Momjian 2000-12-20 02:48:09 Re: Re: [HACKERS] Trigger