| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "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 01:22:17 |
| Message-ID: | NEBBIOAJBMEENKACLNPCIELGCCAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Howe | 2000-12-20 02:02:15 | Re: OID Implicit limit |
| Previous Message | Paul A Vixie | 2000-12-20 00:43:05 | Re: performance modality in 7.1 for large text attributes? |