From: Josh Berkus <josh@agliodbs.com>
To: pgsql-sql@postgresql.org
Subject: Re: maximum number of rows in table - what about oid limits?
Date: Wed, 06 Jun 2001 16:09:09 -0700
Message-ID: <web-68254@davinci.ethosmedia.com> (raw)
In-Reply-To: <6257.991867020@sss.pgh.pa.us>
Tom, Stephan,
> What can happen after a wrap is that the OID generated for a
> newly-created object might conflict with some already-existing
> object's
> OID. If that happens, you get a duplicate-key-insertion error on the
> OID index of the relevant system catalog (pg_class, pg_type, etc).
> There is a unique index on OID for each system catalog wherein OID
> is used to identify objects. It doesn't really matter whether the
> same OID is reused in different catalogs or in user tables.
Given this, why bother with system-generated OIDs on user rows at all?
Why not simply reserve the OIDs for the system tables?
Or are you planning to later increase the OIDs to INT8 and start using
them for OODB-analogous behavior on individual records?
> This is certainly not ideal, but it's not nearly as big a problem as
> transaction ID wraparound. You can live with it, whereas right now
> xact ID wraparound is catastrophic. That we gotta work on, soon.
Nothing like reassuring us commercial DB users, Tom. :-P
Can you describe what you're talking about?
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: maximum number of rows in table - what about oid limits?
In-Reply-To: <web-68254@davinci.ethosmedia.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