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

From Pasi Oja-Nisula
Subject Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
Date
Msg-id CAJvus-OiKggdhVF-JSa=gMo8pJSnDJ51WBgrX492z7oGVX+opw@mail.gmail.com
Whole thread Raw
In response to Re: Stored procedure code no longer stored in v14 and v15, changed behaviour  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Views "missing" from information_schema.view_table_usage
Next
From: Erik Wienhold
Date:
Subject: Re: Views "missing" from information_schema.view_table_usage