X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 8C8229F931E for ; Mon, 8 May 2006 15:00:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 64664-08 for ; Mon, 8 May 2006 15:00:29 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id EB0999F931D for ; Mon, 8 May 2006 15:00:28 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 2FBAB56423; Mon, 8 May 2006 13:00:27 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Mon, 8 May 2006 13:00:26 -0500 Date: Mon, 8 May 2006 13:00:26 -0500 From: "Jim C. Nasby" To: Francesco Dalla Ca' Cc: pgsql-admin@postgresql.org Subject: Re: OIDs wraparaound: postgresql (different versions) behavior Message-ID: <20060508180026.GZ99570@pervasive.com> References: <445F18C5.1090709@cineca.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <445F18C5.1090709@cineca.it> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060508:f.dallaca@cineca.it::1ZXT/IYxprwSFXKl:000000000000000000 0000000000000000000000001Nxu X-Hashcash: 1:20:060508:pgsql-admin@postgresql.org::qshrkC+nVgImu8Qg:00000000000 000000000000000000000000633j X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/69 X-Sequence-Number: 21601 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@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461