Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e943hrG44863 for ; Tue, 3 Oct 2000 23:43:53 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e943hpB02479; Tue, 3 Oct 2000 23:43:51 -0400 (EDT) To: josh@agliodbs.com cc: sqllist , Jeff MacDonald Subject: Re: OID Perfomance - Object-Relational databases In-reply-to: <39DA7ACB.EA4D0B3E@agliodbs.com> References: <39DA03EA.7A1027E8@agliodbs.com> <29675.970600245@sss.pgh.pa.us> <39DA7ACB.EA4D0B3E@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Tue, 03 Oct 2000 17:33:15 -0700" Date: Tue, 03 Oct 2000 23:43:51 -0400 Message-ID: <2476.970631031@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/48 Josh Berkus writes: > SO I'm concerned about the problems you mentioned above. pg_dump has a > -o option; are there problems with this? And how liekly are counter > overflow problems? The trouble with pg_dump -o is that after reload, the OID generator will be set to max(any OID in the dumped data). So a dump & reload doesn't do anything to postpone OID-wraparound Ragnarok. As for the likelihood of overflow, figure 4G / tuple creation rate for your installation (not database, but whole installation controlled by one postmaster). Unless your installation has just one active table, per-table sequence values look like a better bet. BTW, there *is* talk of providing an 8-byte-OID option, but I'm not holding my breath for it. regards, tom lane