pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Spiegelberg <gspiegelberg@cranel.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: OID assistance
Date: Fri, 18 Feb 2005 11:27:24 -0500
Message-ID: <4216176C.4040709@cranel.com> (raw)
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>

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.




view thread (8+ messages)  latest in thread

Message-ID: <4216176C.4040709@cranel.com>
Permalink:  ../4216176C.4040709@cranel.com/
Also on:    postgresql.org/message-id/4216176C.4040709@cranel.com

 · 

reply

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: gspiegelberg@cranel.com, tgl@sss.pgh.pa.us
  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>

* 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