From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
Subject: Re: Solving OID wrap-around in 7.4 DB?
Date: Tue, 18 Oct 2005 12:13:51 -0400
Message-ID: <20051018161351.GG3441@phlogiston.dyndns.org> (raw)
In-Reply-To: <43523940.6080403@endpoint.com>
References: <43523940.6080403@endpoint.com>
On Sun, Oct 16, 2005 at 07:28:00AM -0400, Jeff Boes wrote:
> On behalf of a previous employer who, due to major downsizing, is left
> without an answer to this:
>
> What's the best way to treat impending OID wrap-around in a 7.4.8
> database? This DB has been online for about 18 months, and is expected
> to hit the dreaded wrap-around in about a month. At an application
How many OIDs have been recovered? If the answer is "none" (i.e. the
database doesn't have many deletes), then there isn't likely much you
can do about it -- reloading the database is going to cause the same
problem.
As Chris says in another message, you can use Slony to replicate the
database, in order not to have a long outage. Note, too, that since
you say most tables don't actually use this pg_oid_status method, you
can get away with creating most of the tables without OIDs, which
will stave off your problem for a while. That'd probably even help
if the database mostly just grows, depending (of course) on where the
growth is.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
Information security isn't a technological problem. It's an economics
problem.
--Bruce Schneier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: Solving OID wrap-around in 7.4 DB?
In-Reply-To: <20051018161351.GG3441@phlogiston.dyndns.org>
References: <43523940.6080403@endpoint.com> <20051018161351.GG3441@phlogiston.dyndns.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox