X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 758698BA2B5 for ; Fri, 18 Feb 2005 14:53:11 +0000 (GMT) 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 28218-10 for ; Fri, 18 Feb 2005 14:53:03 +0000 (GMT) Received: from COLSWEEPER.cranel.com (newmail.cranel.com [66.192.200.227]) by svr1.postgresql.org (Postfix) with ESMTP id 31D678B9EAE for ; Fri, 18 Feb 2005 14:53:06 +0000 (GMT) Received: from colmail01.cranel.local (colmail01.cranel.local) by COLSWEEPER.cranel.com (Content Technologies SMTPRS 4.3.14) with ESMTP id ; Fri, 18 Feb 2005 09:51:18 -0500 Received: from [192.168.11.134] (192.168.11.134 [192.168.11.134]) by colmail01.cranel.local with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id 18ST1DQP; Fri, 18 Feb 2005 09:52:37 -0500 Message-ID: <42160081.5050205@cranel.com> Date: Fri, 18 Feb 2005 09:49:37 -0500 From: Greg Spiegelberg Organization: Cranel, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: OID assistance References: <3482911A44F0C44EABC658E136A2E8073E974A@colmail01.cranel.local> <17940.1108738126@sss.pgh.pa.us> In-Reply-To: <17940.1108738126@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200502/164 X-Sequence-Number: 16332 Tom Lane wrote: > "Spiegelberg, Greg" writes: > >>It's come to our attention that in 14-16 days our OID's will wrap around and >>we need some advice. > > > Are you actually using the OIDs for anything? If not, don't worry about > it. We use OID's to store files in the database. Does that qualify? > Unless you are actually depending on OIDs to be unique in some of your > user tables, wraparound shouldn't matter. The only possible bad > consequence is that you might once in a while get a collision in the > system tables (eg, a CREATE TABLE fails because the OID generated for > the table conflicts with an existing table). The odds of that are small > enough that it's probably not going to be as much of a problem as a > dump/reload would be. Just retry the transaction and it'll usually > work the next time. Retrying the transaction isn't something we want to worry about. Our code doesn't have that capability built into it. I read a mailing list article from a while back and there was mentioned in it the possibility of OID's becoming a INT8. Does this exist in any of the new versions? Greg -- Greg Spiegelberg Product Development Manager Cranel, Incorporated. Phone: 614.318.4314 Fax: 614.431.8388 Email: gspiegelberg@cranel.com Technology. Integrity. Focus.