Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f5CGdIE43922 for ; Tue, 12 Jun 2001 12:39:18 -0400 (EDT) (envelope-from pgsql-general-owner@postgresql.org) Received: from web10004.mail.yahoo.com (web10004.mail.yahoo.com [216.136.130.40]) by postgresql.org (8.11.3/8.11.1) with SMTP id f56IjAE75684 for ; Wed, 6 Jun 2001 14:45:10 -0400 (EDT) (envelope-from jmscott@yahoo.com) Message-ID: <20010606184508.46169.qmail@web10004.mail.yahoo.com> Received: from [207.168.117.32] by web10004.mail.yahoo.com; Wed, 06 Jun 2001 11:45:08 PDT Date: Wed, 6 Jun 2001 11:45:08 -0700 (PDT) From: John Scott Reply-To: john@august.com Subject: Re: [SQL] maximum number of rows in table - what about oid limits? To: Stephan Szabo Cc: pgsql-general@postgresql.org, pgsql-sql@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200106/422 X-Sequence-Number: 10789 well i wasn't interested in using oids in my application. i was curious about the relationship oids and the tuple/row limit. i guess if what you say is true, the oids are NOT used internally by postgres. this seems odd. so, i guess my question still stands ... what happens when oids wrap? are oids nothing more than a sequence with an index, not used at all internally? i --- Stephan Szabo wrote: > > On 6 Jun 2001, jmscott@REMOVEMEyahoo.com wrote: > > > postgresql docs claim an essentially unlimited number of > > rows per table. > > > > http://postgresql.crimelabs.net/users-lounge/limitations.html > > > > this doesn't make sense if each row has an oid. > > do more subtle side effects exist if the oid wraps? > > In general, unless you're relying on unique oids, you should be fine. > You probably don't want to use oid as a unique key in your tables for that > reason. Of course, sequences aren't sufficient either (also being > int4) but some kind of int8 "sequence" mechanism would do it if you expect > more than the int4 number of rows. > > You might have problems with creating system table entries with unique > oids after wraparound, but generally that can be fixed by trying again. > (Some of the system tables have a unique index on oid). > ===== John Scott (john@august.com) Senior Partner August Associates email: john@august.com web: http://www.august.com/~jmscott __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/