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

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Dominique Devienne <ddevienne(at)gmail(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "Martijn Tonies (Upscene Productions)" <m(dot)tonies(at)upscene(dot)com>, 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-01 19:08:23
Message-ID: 0730410A-9C79-4EE2-B21B-3502445A8700@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Dec 1, 2022, at 11:05, Dominique Devienne <ddevienne(at)gmail(dot)com> wrote:
>
> I see. Still, Oracle preserves SQL as-is. SQLite preserve SQL as-is.
> Would be nice if PostgreSQL did too. That's all I'm saying.

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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dominique Devienne 2022-12-01 19:20:07 Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
Previous Message David G. Johnston 2022-12-01 19:06:19 Re: how to secure pg_hba.conf