From: Jeff Boes <jeff@endpoint.com>
To: pgsql-admin@postgresql.org
Subject: Solving OID wrap-around in 7.4 DB?
Date: Sun, 16 Oct 2005 07:28:00 -0400
Message-ID: <43523940.6080403@endpoint.com> (raw)
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
level, there's some small chance that OID wrap will cause failures:
there's code that writes rows, and (for tables without primary keys)
relies on DBD::Pg's pg_oid_status method to identify the last INSERT.
(The vast majority of the code does not rely on this, but there's a tiny
fraction that does, and rewriting the code to remove this is not an
option due to the aforementioned downsizing.)
My immediate take on this is that the only sure way to avoid the problem
would be to dump and reload the database. Due to the size of the
database, this is likely to take most of a day. Any other options?
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: jeff@endpoint.com
Subject: Re: Solving OID wrap-around in 7.4 DB?
In-Reply-To: <43523940.6080403@endpoint.com>
References: <43523940.6080403@endpoint.com>
* 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