Re: Handling OID Changes in Regression Tests for C Extensions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Handling OID Changes in Regression Tests for C Extensions
Date
Msg-id 1629026.1749914431@sss.pgh.pa.us
Whole thread Raw
In response to Re: Handling OID Changes in Regression Tests for C Extensions  (Tomas Vondra <tomas@vondra.me>)
List pgsql-hackers
Tomas Vondra <tomas@vondra.me> writes:
> On 6/14/25 11:43, Lakshmi Narayana Velayudam wrote:
>> I am facing a challenge related to OID changes in regression tests while
>> working on a PostgreSQL C extension. Whenever I add or remove a function
>> to the SQL file, it alters OIDs and leads to cascading modifications in
>> multiple test files. This creates a significant overhead in maintaining
>> the regression tests.

> The OIDs for user-defined objects (e.g. those from extensions) are not
> stable, and this will not change. The only way is to prevent the test
> output, e.g. by not including OIDs in the results, and eliminating all
> other types of non-determinism - eg. by enforcing ordering, etc.

You could also make your tests print database object OIDs in
symbolic form, e.g. cast function OIDs to regprocedure, use
pg_describe_object(), etc.  Then it doesn't matter if the
underlying numbers change.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Next
From: Dilip Kumar
Date:
Subject: Re: Replication slot is not able to sync up