From: John Scott <jmscott@yahoo.com>
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: john@august.com
Cc: pgsql-general@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] maximum number of rows in table - what about oid limits?
Date: Wed, 6 Jun 2001 14:52:34 -0700 (PDT)
Message-ID: <20010606215234.97024.qmail@web10001.mail.yahoo.com> (raw)
In-Reply-To: <Pine.BSF.4.21.0106061146090.16690-100000@megazone23.bigpanda.com>
--- Stephan Szabo <sszabo@megazone23.bigpanda.com> wrote:
> On Wed, 6 Jun 2001, John Scott wrote:
>
> > 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?
>
> They are used for references between system tables. That's why
> you'll get intermittent failures on things like create statements after
> rollover (system tables may have unique index on oid).
> As far as I know the system doesn't do stuff with the oid on user rows.
>
>
hmmm. guess i'm still not getting a clear picture on what
happens when oid's wrap? just seems like an obvious question.
if i wrap twice, things could get very wicked, indeed.
if i'm not comfortable with oid wrapping, then doesn't this imply
that postgres can only handle 2^32 tuples (or 2^31 - 1) -
this number of rows per table is relatively small by today's PC standards.
just converting/bulk loading an existing large commercial database into
postgres would expose this issue ;-)
what am i missing here? i am comfortable not using oids
in application logic. that' pretty standard.
my question is, since oid's are used by the
postgres kernel, what effect does oid wrapping have upon
the stability of the database. for example, does oid wrapping mean
i might clash with oid's in the system tables.
i'll poke around the source. just hoped somebody could
shed some light on what seemed like an obvious question.
thanks-john
=====
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/
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-sql@postgresql.org
Cc: jmscott@yahoo.com, sszabo@megazone23.bigpanda.com, john@august.com, pgsql-general@postgresql.org
Subject: Re: [SQL] maximum number of rows in table - what about oid limits?
In-Reply-To: <20010606215234.97024.qmail@web10001.mail.yahoo.com>
References: <Pine.BSF.4.21.0106061146090.16690-100000@megazone23.bigpanda.com> <20010606215234.97024.qmail@web10001.mail.yahoo.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