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 2CF388B9F57 for ; Fri, 18 Feb 2005 16:40:44 +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 63229-10 for ; Fri, 18 Feb 2005 16:40:38 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 97BEA8B9F48 for ; Fri, 18 Feb 2005 16:40:37 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j1IGeaY0018970; Fri, 18 Feb 2005 11:40:36 -0500 (EST) To: Greg Spiegelberg Cc: pgsql-admin@postgresql.org Subject: Re: OID assistance In-reply-to: <4216176C.4040709@cranel.com> 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> <4216176C.4040709@cranel.com> Comments: In-reply-to Greg Spiegelberg message dated "Fri, 18 Feb 2005 11:27:24 -0500" Date: Fri, 18 Feb 2005 11:40:36 -0500 Message-ID: <18969.1108744836@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/170 X-Sequence-Number: 16338 Greg Spiegelberg writes: > 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. Actually, I think the lo_import() will fail anyway, whether you like it or not. There's a unique index on pg_largeobject. > 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? When you're two major versions behind, you don't have a lot of leeway to complain about why things are still an issue ;-). But the short answer is that making OIDs 8 bytes would permanently break platforms that don't have int64 support, and be a nontrivial performance hit on those where int64 is substantially slower than int32. So I'd say it's a good ways into the future yet. Eventually we'll decide we don't care about 32-bit machines anymore, but not for awhile. regards, tom lane