Re: Problem with OID wrap

From: Martin Weinberg <weinberg(at)osprey(dot)astro(dot)umass(dot)edu>
To: pgsql-general(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martin Weinberg <weinberg(at)osprey(dot)astro(dot)umass(dot)edu>
Subject: Re: Problem with OID wrap
Date: 2001-12-15 03:36:25
Message-ID: 200112150336.WAA11873@osprey.astro.umass.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote on Fri, 14 Dec 2001 10:54:09 EST
>Martin Weinberg <weinberg(at)osprey(dot)astro(dot)umass(dot)edu> writes:
>> It seems that OID in one of our databases wrapped during a data
>> load from tape.
>> The wrap is quite plausible based on the volume of the database and
>> the number of tables that have been loaded and reloaded. I would have
>> thought that an OID wrap would be harmless (except in the loss of
>> uniqueness and meaning for any query which depended on this).
>> However, the user complains that part of the table disappeared? Is
>> this possible?
>
>I'd be wondering about transaction ID wrap, myself. You might care
>to consult the discussion of transaction ID wrap in the 7.2 development
>docs (under admin guide "routine maintenance", IIRC).
>

Sound like the best thing to do is to move to 7.2beta as soon as
possible. A dump and a re-initdb will be painful on a regular basis.
The 7.2 strategy seems reasonable and should work fine for us.
Ironically, it turns out that we don't use the transactional features
anyway. Is there a way in the mean time to disable this in 7.1.3?

Thanks Tom!

--Martin

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Gould 2001-12-15 04:10:38 Re: 7.2 back to 7.1.3
Previous Message Josh Berkus 2001-12-15 00:48:02 Re: Vacuum