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 CDD6CDA51A for ; Sun, 16 Oct 2005 08:28:08 -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 38566-02 for ; Sun, 16 Oct 2005 11:28:03 +0000 (GMT) Received: from qtm.net (mummra.qtm.net [216.163.32.14]) by svr1.postgresql.org (Postfix) with SMTP id 61278DA514 for ; Sun, 16 Oct 2005 08:28:04 -0300 (ADT) Received: (qmail 96910 invoked from network); 16 Oct 2005 11:27:59 -0000 Received: from unknown (HELO ?192.168.0.101?) (mur@216.163.42.222) by mummra.qtm.net with SMTP; 16 Oct 2005 11:27:59 -0000 Message-ID: <43523940.6080403@endpoint.com> Date: Sun, 16 Oct 2005 07:28:00 -0400 From: Jeff Boes Organization: End Point, Inc. User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Solving OID wrap-around in 7.4 DB? X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.038 required=5 tests=[AWL=0.038] X-Spam-Level: X-Archive-Number: 200510/176 X-Sequence-Number: 19248 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?