From 2193a856a229026673cbc56310cd0bddf7b5ea25 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Wed, 13 Apr 2005 18:54:57 +0000 Subject: Simplify initdb-time assignment of OIDs as I proposed yesterday, and avoid encroaching on the 'user' range of OIDs by allowing automatic OID assignment to use values below 16k until we reach normal operation. initdb not forced since this doesn't make any incompatible change; however a lot of stuff will have different OIDs after your next initdb. --- src/backend/storage/lmgr/lock.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/backend/storage') diff --git a/src/backend/storage/lmgr/lock.c b/src/backend/storage/lmgr/lock.c index 0073666216..7c7b2b1abd 100644 --- a/src/backend/storage/lmgr/lock.c +++ b/src/backend/storage/lmgr/lock.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/storage/lmgr/lock.c,v 1.148 2005/03/11 03:52:06 neilc Exp $ + * $PostgreSQL: pgsql/src/backend/storage/lmgr/lock.c,v 1.149 2005/04/13 18:54:56 tgl Exp $ * * NOTES * Outside modules can create a lock table and acquire/release @@ -97,7 +97,7 @@ static const char *const lock_mode_names[] = * -------- */ -int Trace_lock_oidmin = BootstrapObjectIdData; +int Trace_lock_oidmin = FirstNormalObjectId; bool Trace_locks = false; bool Trace_userlocks = false; int Trace_lock_table = 0; -- cgit v1.2.1