Re: Conservation of OIDs - Mailing list pgsql-general

From Manfred Koizar
Subject Re: Conservation of OIDs
Date
Msg-id 8i1arvgnj2m1turr7qfjo9rr21a8nou7h7@email.aon.at
Whole thread Raw
In response to Conservation of OIDs  (<btober@seaworthysys.com>)
Responses Re: Conservation of OIDs  (<btober@seaworthysys.com>)
Re: Conservation of OIDs  (<btober@seaworthysys.com>)
List pgsql-general
On Fri, 14 Nov 2003 10:01:51 -0500 (EST), <btober@seaworthysys.com>
wrote:
>The Production database is the "real" data, and we periodically take a
>back up from Prod and re-instantiate QAT and DEV by dropping them and
>then restoring from the Prod backup.

> Not that OID's are in short supply,
>but I'm anal retentive about these things and so if there is a
>straight-forward way to avoid unnecesary OID consumption it would help me
>sleep better.

OIDs are unsigned 32 bit.  Something like 1000 or 10000 are reserved
for system use.  So you still have more than 4000000000 for your
objects.  How many objects (tables, indices, operators, functions,
...) are there, and how often is "periodically"?

If you're really concerned, you can initdb separate clusters for QAT
and DEV and run three postmasters using three different ports.

Servus
 Manfred

pgsql-general by date:

Previous
From: "Thomas LeBlanc"
Date:
Subject: Loggin SQL Statements from JBOSS/JDBC
Next
From: Richard Huxton
Date:
Subject: Re: Loggin SQL Statements from JBOSS/JDBC