X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 37AAB11F66F8 for ; Mon, 17 Apr 2006 19:09:27 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.239 X-Spam-Level: X-Spam-Status: No, score=0.239 required=5 tests=[AWL=0.239] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id H6zm1LCDR058 for ; Mon, 17 Apr 2006 19:09:17 -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 678AE11F66E7 for ; Mon, 17 Apr 2006 19:09:19 -0300 (ADT) Received: from [172.16.5.102] (64-132-13-2.gen.twtelecom.net [64.132.13.2]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by noel.decibel.org (Postfix) with ESMTP id E9E1C56408; Mon, 17 Apr 2006 17:09:18 -0500 (CDT) In-Reply-To: <4551.1145303173@sss.pgh.pa.us> References: <20060417193829.GN49405@pervasive.com> <4551.1145303173@sss.pgh.pa.us> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit From: Jim Nasby Subject: Re: DDL commands don't handle OID wrap Date: Mon, 17 Apr 2006 17:09:15 -0500 To: Tom Lane X-Mailer: Apple Mail (2.749.3) X-Archive-Number: 200604/151 X-Sequence-Number: 21320 On Apr 17, 2006, at 2:46 PM, Tom Lane wrote: > "Jim C. Nasby" writes: >> Haven't seen this in previous discussions of OID wrap in the >> archives. >> The issue is that DDL statements don't make any attempt to skip past >> used ranges of OIDs. >> duplicate key violates unique constraint "pg_attrdef_oid_index" > > If you can make that happen in 8.1, I'd be fascinated to look at the > test case. Yet another reason for this customer to upgrade... :) Also, in 8.1, here's a list of tables in pg_catalog that don't appear to have unique constraints on oid... do these all look safe? decibel=# select table_name from information_schema.tables where table_schema='pg_catalog' and table_type='BASE TABLE' except select tablename from pg_indexes where schemaname='pg_catalog' and indexname like '%oid%'; table_name ----------------- pg_amop pg_amproc pg_attribute pg_auth_members pg_autovacuum pg_depend pg_description pg_index pg_inherits pg_listener pg_pltemplate pg_shdepend pg_statistic -- Jim C. Nasby, Database Architect decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"