Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f572DLE21790 for ; Wed, 6 Jun 2001 22:13:21 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f572DBR06675; Wed, 6 Jun 2001 22:13:12 -0400 (EDT) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: maximum number of rows in table - what about oid limits? In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Wed, 06 Jun 2001 16:09:09 -0700" Date: Wed, 06 Jun 2001 22:13:11 -0400 Message-ID: <6671.991879991@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/90 X-Sequence-Number: 3309 "Josh Berkus" 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