From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Francesco Dalla Ca' <f(dot)dallaca(at)cineca(dot)it> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: OIDs wraparaound: postgresql (different versions) behavior |
Date: | 2006-05-08 18:00:26 |
Message-ID: | 20060508180026.GZ99570@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, May 08, 2006 at 12:09:13PM +0200, Francesco Dalla Ca' wrote:
> The PostgreSQL manual explain that from 8.1 the default behavior
> (governed by default_with_oids system parameter) is to create user
> tables "without oids".
>
> Well, at the page
> http://www.postgresql.org/docs/8.1/interactive/datatype-oid.html , the
> manual report this:
> "Object identifiers (OIDs) are used internally by PostgreSQL as primary
> keys for various system tables."
>
> What do i look and take care about the OID wraparound phenomenon? (On a
> DBA perspective)
> There is a possibility for a data inconsistency? (Or possibles database
> blocking errors?)
> What's the differents server behaviors for this phenomenon on differents
> realeases?
In older versions if you wrapped the OID counter you'd get an error
about 'unable to create file' when you tried to create a new object and
the OID counter was pointing at a OID that had been used for another
object. That's fixed in 8.1.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Krajmalnik | 2006-05-08 20:42:20 | PostgreSQL 8.1.3/Windows |
Previous Message | Tom Lane | 2006-05-08 14:49:19 | Re: Meaning of contexts from pg_settings view |