Skip site navigation (1) Skip section navigation (2)

To OID or not to OID

From: "David Parker" <dparker(at)tazznetworks(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: To OID or not to OID
Date: 2004-09-28 14:02:03
Message-ID: 07FDEE0ED7455A48AC42AC2070EDFF7C0C03EE@corpsrv2.tazznetworks.com (view raw or flat)
Thread:
Lists: pgsql-general
I've been looking through the archives for guidance on whether or not we
should create our tables WITHOUT OIDS. I've seen some discussions about
making WITHOUT the default for user tables, and seen some caveats about
the oid int value wrapping, etc., but I haven't been able to find a
discussion of the relative merits (I'm sure there's been one....)

Is there any concrete reason NOT to create tables WITHOUT OIDS? We are
going to have some very large tables in our app, so saving the space and
not worrying about int-wrap seems like a good idea, but I'm worried that
I'm missing something.

-  DAP
====================================================== 
David Parker    Tazz Networks    (401) 709-5130
 

Responses

pgsql-general by date

Next:From: frederic.germaneauDate: 2004-09-28 14:03:26
Subject: postgres v8b├ęta3 on AIX5.2
Previous:From: Randy YatesDate: 2004-09-28 13:30:08
Subject: Re: Foreign key order evaluation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group