Re: Proposal: OID wraparound: summary and proposal
| От | Hannu Krosing |
|---|---|
| Тема | Re: Proposal: OID wraparound: summary and proposal |
| Дата | |
| Msg-id | 3B6F7804.5A0CD46A@tm.ee обсуждение исходный текст |
| Ответ на | Re: Proposal: OID wraparound: summary and proposal (Neil Tiffin <ntiffin@earthlink.net>) |
| Ответы |
Re: Proposal: OID wraparound: summary and proposal
|
| Список | pgsql-hackers |
Neil Tiffin wrote: > > I would just like to comment that for our project, GNU Enterprise, we > use our own 128 bit object ID that is unique (UUID) for every row in > all tables. > > It seems to me, without having looked into it, that having both a > PostgreSQL UID and our own 128 bit objectid (UUID) is redundant and > slows the whole process down. But we are storing object data in the > database and require and absolutely unique objectid. We are planning > for enterprise usage and expect to need 128 bits to uniquely define > our objects. Is it just an 128-bit int from a sequence or does it have some internal structure ? What kind of enterprise do you expect to have more than 18 446 744 073 709 551 615 of objects that can uniquely be identified by 64 bits ? ------------- Hannu
В списке pgsql-hackers по дате отправления: