From: Tom Lane <tgl@sss.pgh.pa.us>
To: Spiegelberg, Greg <gspiegelberg@cranel.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: OID assistance
Date: Fri, 18 Feb 2005 09:48:46 -0500
Message-ID: <17940.1108738126@sss.pgh.pa.us> (raw)
In-Reply-To: <3482911A44F0C44EABC658E136A2E8073E974A@colmail01.cranel.local>
References: <3482911A44F0C44EABC658E136A2E8073E974A@colmail01.cranel.local>
"Spiegelberg, Greg" <gspiegelberg@cranel.com> writes:
> It's come to our attention that in 14-16 days our OID's will wrap around and
> we need some advice.
Are you actually using the OIDs for anything? If not, don't worry about
it.
Unless you are actually depending on OIDs to be unique in some of your
user tables, wraparound shouldn't matter. The only possible bad
consequence is that you might once in a while get a collision in the
system tables (eg, a CREATE TABLE fails because the OID generated for
the table conflicts with an existing table). The odds of that are small
enough that it's probably not going to be as much of a problem as a
dump/reload would be. Just retry the transaction and it'll usually
work the next time.
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, gspiegelberg@cranel.com
Subject: Re: OID assistance
In-Reply-To: <17940.1108738126@sss.pgh.pa.us>
References: <3482911A44F0C44EABC658E136A2E8073E974A@colmail01.cranel.local> <17940.1108738126@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