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

From: "Martijn Tonies \(Upscene Productions\)" <m(dot)tonies(at)upscene(dot)com>
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-05 10:55:24
Message-ID: 6686077EEDC543C6ACEB072468E3538D@MARTIJNWS
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>Also, we've *never* had storage of the original text for views.
>I'm a little mystified by people claiming they use original
>text for vetting functions when they clearly have no equivalent
>ability for views ... or are your applications completely
>view-free?

Well, I would say that's annoying too!

>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.

Do note, that pg_get_viewdef returns the SELECT statement of a view,
no column name specification, while pg_get_function_def returns a CREATE
statement.

So the implementation is different too.

With regards,

Martijn Tonies
Upscene Productions
https://www.upscene.com

Database Workbench - developer tool for Oracle, SQL Server, PostgreSQL,
MySQL, InterBase, NexusDB and Firebird.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2022-12-05 12:15:38 Re: plpgsql_check_function issue after upgrade
Previous Message Daniel Verite 2022-12-05 10:51:34 Re: Q: error on updating collation version information