From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Spiegelberg <gspiegelberg@cranel.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: OID assistance
Date: Fri, 18 Feb 2005 11:40:36 -0500
Message-ID: <18969.1108744836@sss.pgh.pa.us> (raw)
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>
Greg Spiegelberg <gspiegelberg@cranel.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, gspiegelberg@cranel.com
Subject: Re: OID assistance
In-Reply-To: <18969.1108744836@sss.pgh.pa.us>
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> <18969.1108744836@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox