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 E37D98BA100 for ; Fri, 18 Feb 2005 16:30:59 +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 60044-09 for ; Fri, 18 Feb 2005 16:30:54 +0000 (GMT) Received: from COLSWEEPER.cranel.com (newmail.cranel.com [66.192.200.227]) by svr1.postgresql.org (Postfix) with ESMTP id 3B8498BA09B for ; Fri, 18 Feb 2005 16:30:53 +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 11:29:07 -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 18ST11XV; Fri, 18 Feb 2005 11:30:25 -0500 Message-ID: <4216176C.4040709@cranel.com> Date: Fri, 18 Feb 2005 11:27:24 -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> <42160081.5050205@cranel.com> <18094.1108738956@sss.pgh.pa.us> <42160FA7.8030607@cranel.com> <18727.1108743554@sss.pgh.pa.us> In-Reply-To: <18727.1108743554@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/169 X-Sequence-Number: 16337 Tom Lane wrote: > Well, put a unique index on the contents column. Better to fail an > insert than to get a conflict of LO OIDs. Can't do that. Our app won't handle it. > If you were on 7.4 or later you could do ALTER TABLE SET WITHOUT OIDS so > you'd not be sucking up OIDs for the table rows themselves. On 7.3 the > only way would be to drop and recreate the larger tables WITHOUT OIDS, > which is probably going to be painful :-(. I figured as much. We're working to automate the dump-restore-alter table process now. This does lead me to 2 questions... first, why is this still an issue and not fixed in the backend where OID's are managed? Second, shouldn't there be something like "use WITHOUT OIDS for data warehouses" be in the FAQ? Thanks for the quick response. Greg -- Greg Spiegelberg Product Development Manager Cranel, Incorporated. Phone: 614.318.4314 Fax: 614.431.8388 Email: gspiegelberg@cranel.com Technology. Integrity. Focus.