From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: sqllist <pgsql-sql@postgresql.org>
Cc: Jeff MacDonald <jeff@pgsql.com>
Subject: Re: OID Perfomance - Object-Relational databases
Date: Tue, 03 Oct 2000 23:43:51 -0400
Message-ID: <2476.970631031@sss.pgh.pa.us> (raw)
In-Reply-To: <39DA7ACB.EA4D0B3E@agliodbs.com>
References: <39DA03EA.7A1027E8@agliodbs.com>
<29675.970600245@sss.pgh.pa.us>
<39DA7ACB.EA4D0B3E@agliodbs.com>
Josh Berkus <josh@agliodbs.com> 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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, jeff@pgsql.com
Subject: Re: OID Perfomance - Object-Relational databases
In-Reply-To: <2476.970631031@sss.pgh.pa.us>
References: <39DA03EA.7A1027E8@agliodbs.com> <29675.970600245@sss.pgh.pa.us> <39DA7ACB.EA4D0B3E@agliodbs.com> <2476.970631031@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