Re: Stored procedure code no longer stored in v14 and v15, changed behaviour

Dominique Devienne <ddevienne(at)gmail(dot)com> writes:
> On Thu, Dec 1, 2022 at 8:09 PM Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>> Since this is a custom-built system, there is nothing keeping you from creating your own table in the database that stores the original text of the function.

> That's not the point. If a DBA updates one of our triggers or proc or
> whatever else,
> the recorded info in a custom table won't be affected. We are diff'ing
> the server-side
> schema, against the expected in-memory model of the physical model.

> Thus the dictionaries are the only source of truth we can trust for
> the current state of the schema.
> And beside minor syntactic differences, and some more troublesome
> object-name rewrites, this is
> exactly what we want. The system itself needs to preserve the original
> DDL IMHO. --DD

Do you really fail to see the contradictions in this? You want the
database to preserve the original DDL, but you also want it to update
in response to subsequent alterations. You can't have both those
things.

regards, tom lane