pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Martijn Tonies \(Upscene Productions\) <m.tonies@upscene.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
Date: Mon, 5 Dec 2022 11:55:24 +0100
Message-ID: <6686077EEDC543C6ACEB072468E3538D@MARTIJNWS> (raw)
In-Reply-To: <1937424.1669996938@sss.pgh.pa.us>
References: <23DE96C56DFC404096553A22DDC5093B@MARTIJNWS>
	<CAKFQuwbYCk0oA3VT+ngEebBTBjdtGsVLEFOdPX2qqQJobA7rtg@mail.gmail.com>
	<1579912.1669908194@sss.pgh.pa.us>
	<CAFCRh--K2tahGetbJ_mtjiwvfFb9fF6SzjGnvbyoMKPr92FiTQ@mail.gmail.com>
	<Y4lFsaF3xz24K0mr@raf.org>
	<CAJvus-MKW1tFhnotbQXbvCdXbfgH6WpvmExsMrYi1Yfov85KOA@mail.gmail.com>
	<Y4oB5RLrbTFLGWsW@raf.org>
	<CAJvus-O6qvF_3jNHZdfX5f-5s3FLSHhUHVyPYtgCzftYH+CYXg@mail.gmail.com>
	<1937424.1669996938@sss.pgh.pa.us>

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






view thread (37+ messages)

Message-ID: <6686077EEDC543C6ACEB072468E3538D@MARTIJNWS>
Permalink:  ../6686077EEDC543C6ACEB072468E3538D@MARTIJNWS/
Also on:    postgresql.org/message-id/6686077EEDC543C6ACEB072468E3538D@MARTIJNWS

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: m.tonies@upscene.com
  Subject: Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
  In-Reply-To: <6686077EEDC543C6ACEB072468E3538D@MARTIJNWS>
  References: <23DE96C56DFC404096553A22DDC5093B@MARTIJNWS> <CAKFQuwbYCk0oA3VT+ngEebBTBjdtGsVLEFOdPX2qqQJobA7rtg@mail.gmail.com> <1579912.1669908194@sss.pgh.pa.us> <CAFCRh--K2tahGetbJ_mtjiwvfFb9fF6SzjGnvbyoMKPr92FiTQ@mail.gmail.com> <Y4lFsaF3xz24K0mr@raf.org> <CAJvus-MKW1tFhnotbQXbvCdXbfgH6WpvmExsMrYi1Yfov85KOA@mail.gmail.com> <Y4oB5RLrbTFLGWsW@raf.org> <CAJvus-O6qvF_3jNHZdfX5f-5s3FLSHhUHVyPYtgCzftYH+CYXg@mail.gmail.com> <1937424.1669996938@sss.pgh.pa.us> <6686077EEDC543C6ACEB072468E3538D@MARTIJNWS>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox