Aw: Re: Stored procedure code no longer stored in v14 and v15, changed behaviour - Mailing list pgsql-general

From Karsten Hilbert
Subject Aw: Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
Date
Msg-id trinity-14b76257-6780-433b-8624-c2be32f0d603-1670097346999@3c-app-gmx-bap57
Whole thread Raw
In response to Re: Stored procedure code no longer stored in v14 and v15, changed behaviour  (Alban Hertroys <haramrae@gmail.com>)
Responses Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
List pgsql-general
> You would need to wrap the function creation calls into some automation to generate and store those diffs, comparing
itback, etc, but that may be doable. I would also generate new diffs right after major version updates of the database
(abefore and after of the output of pg_get_functiondef, applied to the stored diff?).
 

I wonder whether that would tie the sanity check to a particular PG version.

I mean, pg_get_functiondef output being a server runtime artifact it might
well change between server versions, no ?

Best,
Karsten




pgsql-general by date:

Previous
From: David Rowley
Date:
Subject: Re: sort performance better with little memory than big memory
Next
From: "jacktby@gmail.com"
Date:
Subject: How to repair my plan modify error?