From: | Manfred Koizar <mkoi-pg(at)aon(dot)at> |
---|---|
To: | <btober(at)seaworthysys(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Conservation of OIDs |
Date: | 2003-11-14 16:51:25 |
Message-ID: | 8i1arvgnj2m1turr7qfjo9rr21a8nou7h7@email.aon.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 14 Nov 2003 10:01:51 -0500 (EST), <btober(at)seaworthysys(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2003-11-14 17:07:37 | Re: Loggin SQL Statements from JBOSS/JDBC |
Previous Message | PhilM | 2003-11-14 16:49:38 | Can Postgresql run under Windows? |