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:19:14 -0500
Message-ID: <18727.1108743554@sss.pgh.pa.us> (raw)
In-Reply-To: <42160FA7.8030607@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>
Greg Spiegelberg <gspiegelberg@cranel.com> writes:
> Tom Lane wrote:
>> Exactly how are you "using OIDs to store files"? Do you mean you're
>> using large objects?
> The table is
> Table "public.imgs"
> Column | Type | Modifiers
> ----------+--------+------------------------------------------------------
> id | bigint | not null default nextval('public.imgs_id_seq'::text)
> file | text |
> contents | oid |
> Indexes: imgs_pkey primary key btree (id)
> Data is loaded using INSERT's.
> insert into imgs values (1,'/path/to/myfile',lo_import('/path/to/myfile'));
Well, put a unique index on the contents column. Better to fail an
insert than to get a conflict of LO OIDs.
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 :-(.
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: <18727.1108743554@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>
* 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