pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Chris Browne <cbbrowne@acm.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: Solving OID wrap-around in 7.4 DB?
Date: Mon, 17 Oct 2005 14:50:01 -0500
Message-ID: <1129578600.32035.5.camel@state.g2switchworks.com> (raw)
In-Reply-To: <60fyr0gjlw.fsf@dba2.int.libertyrms.com>
References: <43523940.6080403@endpoint.com>
	<60fyr0gjlw.fsf@dba2.int.libertyrms.com>

On Mon, 2005-10-17 at 12:04, Chris Browne wrote:
> jeff@endpoint.com (Jeff Boes) writes:
> > 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?
> 
> Another method would be to use replication to load the data into a
> fresh DB instance.
> 
> You could, in principle, use Slony-I to do this; that is an intended
> sort of "use case."

I thought that with 7.4 all you needed was to vacuum all databases (full
maybe???) to prevent oid wraparound.



view thread (5+ messages)  latest in thread

Message-ID: <1129578600.32035.5.camel@state.g2switchworks.com>
Permalink:  ../1129578600.32035.5.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1129578600.32035.5.camel@state.g2switchworks.com

 · 

reply

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: smarlowe@g2switchworks.com, cbbrowne@acm.org
  Subject: Re: Solving OID wrap-around in 7.4 DB?
  In-Reply-To: <1129578600.32035.5.camel@state.g2switchworks.com>
  References: <43523940.6080403@endpoint.com> <60fyr0gjlw.fsf@dba2.int.libertyrms.com> <1129578600.32035.5.camel@state.g2switchworks.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