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

From: Pasi Oja-Nisula <pon(at)iki(dot)fi>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
Date: 2022-12-02 21:15:33
Message-ID: CAJvus-OiKggdhVF-JSa=gMo8pJSnDJ51WBgrX492z7oGVX+opw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> If you want an audit comparison point, I'd suggest capturing
> the result of pg_get_functiondef or one of its sibling functions
> just after creating your function. "pg_dump -s" is another
> pretty credible mechanism for capturing schema details.

That's very good info, thank you. I guess freaking out was unnecessary. Sorry.

So the idea is to do apples to apples comparison and forget the sql source files
with whitespace and comments. When comparing a know good database
I can do pg_get_functiondef in both databases and compare the results.
It's just a matter of how well each query tool can represent diffs or
do results
comparison. pg_dump output is even better for comparison.

Pasi

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Erik Wienhold 2022-12-02 21:33:27 Re: Views "missing" from information_schema.view_table_usage
Previous Message David G. Johnston 2022-12-02 21:14:47 Re: Views "missing" from information_schema.view_table_usage