Postgres Pro
Downloads
Home   >   mailing lists

Re: removing datlastsysoid - Mailing list pgsql-hackers

From Dave Page
Subject Re: removing datlastsysoid
Date
Msg-id CA+OCxoyt-GdtrD4J7cSDGw8Ljko5oz1j1CMH6ogA82RPpbGciA@mail.gmail.com
Whole thread Raw
In response to Re: removing datlastsysoid  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: removing datlastsysoid  (David Steele <david@pgmasters.net>)
List pgsql-hackers
Tree view


On Thu, 20 Jan 2022 at 14:03, Robert Haas <robertmhaas@gmail.com> wrote:
On Mon, Jan 17, 2022 at 3:43 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> +1.  Another reason to get rid of it is that it has nothing to do
> with the system OID ranges defined in access/transam.h.

Agreed. Thanks for looking. Committed.

So we just ran into this whilst updating pgAdmin to support PG15. How is one supposed to figure out what the last system OID is now from an arbitrary database? pgAdmin uses that value in well over 300 places in its source. 

--

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: make MaxBackends available in _PG_init
Next
From: David Steele
Date:
Subject: Re: removing datlastsysoid