Re: DDL commands don't handle OID wrap

From: Jim Nasby <jnasby(at)pervasive(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: DDL commands don't handle OID wrap
Date: 2006-04-17 22:09:15
Message-ID: DFB1560F-60B3-486D-A6C9-14A32D00C5D5@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Apr 17, 2006, at 2:46 PM, Tom Lane wrote:

> "Jim C. Nasby" <jnasby(at)pervasive(dot)com> 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(at)decibel(dot)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?"

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message D Srinivas-in1713c 2006-04-18 02:52:52 Regarding installation of postgresql8.1 on windows XP
Previous Message Bruno Wolff III 2006-04-17 20:47:08 Re: downward dump compatibility