Re: removing datlastsysoid

On 5/16/22 10:26 AM, Tom Lane wrote:
> Dave Page <dpage(at)pgadmin(dot)org> writes:
>> On Mon, 16 May 2022 at 15:06, David Steele <david(at)pgmasters(dot)net> wrote:
>>> Out solution was to use the constant:
>>>
>>> #define FirstNormalObjectId 16384
>>>
>>> And treat anything below that as a system oid. This constant has not
>>> changed in a very long time (if ever) but we added it to our list of
>>> constants to recheck with each release.
>
>> Yes, that seems reasonable. Changing that value would very likely break
>> pg_upgrade I can imagine, so I suspect it'll stay as it is for a while
>> longer.
>
> Yeah, raising that would be extremely painful for pg_upgrade.
>
> I think that when we approach the point where the system OID range
> is saturated, we'll give up the principle of system OIDs being
> globally unique instead of doing that. There's no fundamental
> reason why unique-per-catalog wouldn't be good enough, and letting
> that be the standard would give us many more years of breathing room.
I'm in favor of global IDs since they help prevent incorrect joins, but
agree that what you propose would likely be the least painful solution.

Regards,
--
-David
david(at)pgmasters(dot)net