From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: maximum number of rows in table - what about oid limits?
Date: Wed, 06 Jun 2001 22:13:11 -0400
Message-ID: <6671.991879991@sss.pgh.pa.us> (raw)
In-Reply-To: <web-68254@davinci.ethosmedia.com>
References: <web-68254@davinci.ethosmedia.com>
"Josh Berkus" <josh@agliodbs.com> writes:
> Given this, why bother with system-generated OIDs on user rows at all?
> Why not simply reserve the OIDs for the system tables?
An option to not generate OIDs unless requested (on a table-by-table
basis) has been discussed. It seems like a fine near-term solution
to me. 8-byte OIDs are a longer-term solution, because they'll break
a lot of things (including clients...)
>> 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?
It's in the archives: after 4G transactions, your database curls up
and dies. When your pg_log starts to approach 1Gbyte (2 bits per
transaction) you'd better plan on dump/initdb/reload.
regards, tom lane
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: tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: maximum number of rows in table - what about oid limits?
In-Reply-To: <6671.991879991@sss.pgh.pa.us>
* 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