Re: OID Overflow for large objects
| От | Tom Lane |
|---|---|
| Тема | Re: OID Overflow for large objects |
| Дата | |
| Msg-id | 15078.1083956932@sss.pgh.pa.us обсуждение |
| Ответ на | OID Overflow for large objects (Jeff Boes <jboes@nexcerpt.com>) |
| Ответы |
Re: OID Overflow for large objects
|
| Список | pgsql-admin |
Jeff Boes <jboes@nexcerpt.com> writes: > I found some indication of the problem referenced in the Pg FAQ > (http://www3.sk.postgresql.org/docs/faqs/FAQ.html): > OIDs are stored as 4-byte integers, and will overflow at 4 billion. No > one has reported this ever happening, and we plan to have the limit > removed before anyone does. That comment in the FAQ seems quite out-of-date. What will actually happen is that the OID generator will wrap around. This will not bother Postgres particularly, but you may start having occasional transaction failures due to duplicate OIDs --- for example, I believe lo_create will fail if the OID it selects already exists in pg_largeobject. regards, tom lane
В списке pgsql-admin по дате отправления: