True, but for over a decade Postgres common wisdom has discouraged using the OID for anything in the app level.
As I recall, OIDs only ever came up in practice if you wound up wrapping the 32 bit uint.
As I recall, OIDs only ever came up in practice if you wound up wrapping the 32 bit uint.
The original goal for OID was a bit like UUIDs, but just at the cluster level rather than truly global. Someone steeped in that background and focused on "tuning", where you would consider things like storage consumption and index efficiency for int4 vs int8, might well have baked OIDs into a URL while dismissing the uuid type as extravagantly expensive.