Aw: Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
Karsten Hilbert <karsten.hilbert@gmx.net>
From: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: Alban Hertroys <haramrae@gmail.com>
Cc: DAVID ROTH <adaptron@comcast.net>, Dominique Devienne
<ddevienne@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Christophe Pettus
<xof@thebuild.com>, Adrian Klaver <adrian.klaver@aklaver.com>, Laurenz Albe
<laurenz.albe@cybertec.at>, "David G. Johnston"
<david.g.johnston@gmail.com>, "Martijn Tonies (Upscene Productions)"
<m.tonies@upscene.com>, pgsql-general@lists.postgresql.org
Date: 2022-12-03T19:55:47Z
Lists: pgsql-general
> You would need to wrap the function creation calls into some automation to generate and store those diffs, comparing it back, etc, but that may be doable. I would also generate new diffs right after major version updates of the database (a before 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