From: | "Steve O'Hagan" <sohagan(at)dont-spam-me-stanger(dot)com(dot)hk> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: OID wrap around |
Date: | 2001-05-25 01:07:48 |
Message-ID: | 9ekb6o$1bk9$1@news.tht.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
But when I've finished calculating the 4 billion names of God, it wont
matter anyway - end of universe as we know it . . . ;-)
Regards.
SGO.
<jeff(dot)fitzmyers(at)managestar(dot)com> wrote in message
news:371EAC487A83CD4296F6999FD088D83305B725(at)atlas(dot)managestar(dot)com(dot)(dot)(dot)
> Remembering past discussions: Yes OID's wrap around. When this happens,
> they will not nesecarily be unique anymore. Apparently this should not
> be a problem unless one has queries that specifically use OID's. INT8
> OID's have been talked about and will probably be implemented some day.
>
> Jeff
> >>>>>
> Someone mentioned the OIDs are unique for every row for an entire
> database cluster. I also notice that they are not being reused (like a
> sequence). Will they wrap around as soon as the 2^32 boundary is hit?
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Dr. Evil | 2001-05-25 02:23:50 | Implicit row locking during an UPDATE |
Previous Message | Tatsuo Ishii | 2001-05-25 01:02:51 | Re: Charset and encoding |