X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4B87BD7E11 for ; Tue, 18 Oct 2005 13:13:59 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 95914-08 for ; Tue, 18 Oct 2005 16:13:56 +0000 (GMT) Received: from smtp104.rog.mail.re2.yahoo.com (smtp104.rog.mail.re2.yahoo.com [206.190.36.82]) by svr1.postgresql.org (Postfix) with SMTP id 94527D7E0B for ; Tue, 18 Oct 2005 13:13:56 -0300 (ADT) Received: (qmail 18153 invoked from network); 18 Oct 2005 16:13:56 -0000 Received: from unknown (HELO phlogiston.dydns.org) (a.sullivan@rogers.com@209.222.54.227 with login) by smtp104.rog.mail.re2.yahoo.com with SMTP; 18 Oct 2005 16:13:55 -0000 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id DB64440E6; Tue, 18 Oct 2005 12:13:51 -0400 (EDT) Date: Tue, 18 Oct 2005 12:13:51 -0400 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: Solving OID wrap-around in 7.4 DB? Message-ID: <20051018161351.GG3441@phlogiston.dyndns.org> References: <43523940.6080403@endpoint.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43523940.6080403@endpoint.com> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.033 required=5 tests=[AWL=-0.017, FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200510/212 X-Sequence-Number: 19284 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