From: | Jonathan Bartlett <johnnyb6(at)sdf(dot)lonestar(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: maximum number of rows in table - what about oid limits? |
Date: | 2001-06-07 13:34:24 |
Message-ID: | Pine.LNX.4.21.0106071332360.781-100000@sdf.lonestar.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
Besides compatibility, what breaks when you make OIDs/Txn IDs
INT8s? Maybe there should be a minor fork called Postgres64 which does
this for those needing large tables.
Jon
johnnyb6(at)sdf(dot)lonestar(dot)org
SDF Public Access UNIX System - http://sdf.lonestar.org
On Wed, 6 Jun 2001, Tom Lane wrote:
> "Josh Berkus" <josh(at)agliodbs(dot)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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2001-06-07 14:22:10 | Re: PostgreSQL Replication Server? |
Previous Message | Allan Kamau | 2001-06-07 13:29:45 | Writing transactions in plpgsql |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2001-06-07 13:41:32 | Re: behavior of ' = NULL' vs. MySQL vs. Standards |
Previous Message | fabrizio | 2001-06-07 12:22:05 | which sql syntax is better for joins on pgsql? |