pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: DAVID ROTH <adaptron@comcast.net>
To: Dominique Devienne <ddevienne@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Christophe Pettus <xof@thebuild.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Martijn Tonies (Upscene Productions) <m.tonies@upscene.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
Date: Fri, 2 Dec 2022 09:10:57 -0500 (EST)
Message-ID: <1258414512.930087.1669990257195@connect.xfinity.com> (raw)
In-Reply-To: <CAFCRh--6qhmGKy5j7RVEBWW=r3YCeRm=WogwKxEA6Nhzcc0uDg@mail.gmail.com>
References: <23DE96C56DFC404096553A22DDC5093B@MARTIJNWS>
	<CAKFQuwbYCk0oA3VT+ngEebBTBjdtGsVLEFOdPX2qqQJobA7rtg@mail.gmail.com>
	<1579912.1669908194@sss.pgh.pa.us>
	<CAFCRh--K2tahGetbJ_mtjiwvfFb9fF6SzjGnvbyoMKPr92FiTQ@mail.gmail.com>
	<c14b49a2043adafbe9589fab7af4eceb6199726c.camel@cybertec.at>
	<CAFCRh-8DBZdfq_r+5jX9s8XPGxrANCOuWffkBBadpRTm7VP-OA@mail.gmail.com>
	<bee36d64-84e3-2918-9183-6035e1e6e221@aklaver.com>
	<CAFCRh-_wTu8mdxurTgjVO0Z19Xs1sam0ZFQqdXAJ5eF+7NLkpA@mail.gmail.com>
	<0730410A-9C79-4EE2-B21B-3502445A8700@thebuild.com>
	<CAFCRh-_cNHc0K0zLy6s0H7kaXOwPkC0mK74aXTGA2YOqKi89FA@mail.gmail.com>
	<1697225.1669924271@sss.pgh.pa.us>
	<CAFCRh--6qhmGKy5j7RVEBWW=r3YCeRm=WogwKxEA6Nhzcc0uDg@mail.gmail.com>

Is there a way to reverse engineer the original code (or its equivalent) from what is saved in the database?

> On 12/02/2022 8:48 AM Dominique Devienne <ddevienne@gmail.com> wrote:
> 
>  
> On Thu, Dec 1, 2022 at 8:51 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Do you really fail to see the contradictions in this?  You want the
> > database to preserve the original DDL, but you also want it to update
> > in response to subsequent alterations.  You can't have both those
> 
> Hi. I probably didn't express myself correctly. I don't think there's
> a contradiction.
> 
> I originally wrote:
> "maintaining the original, at least until a re-write is necessary on renames".
> 
> But that I meant that the SQL would be preserved as-is, *initially*.
> But that if/when a rename affecting that SQL happens, then it's fair
> game to re-write it.
> Because then the diff between my in-memory code-generated DDL, and the
> server-side
> DDL is no longer a false positive, as it is now from the "pre-emptive" re-write.
> 
> What is creating me pain, is the fact the re-write of the SQL is
> *eager* instead of *lazy*.
> I.e. I'm paying for the rewrite, even when it's not strictly necessary
> (from my POV at least).
> 
> I hope that makes more sense. Thanks, --DD





view thread (37+ messages)  latest in thread

Message-ID: <1258414512.930087.1669990257195@connect.xfinity.com>
Permalink:  ../1258414512.930087.1669990257195@connect.xfinity.com/
Also on:    postgresql.org/message-id/1258414512.930087.1669990257195@connect.xfinity.com

 · 

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: adaptron@comcast.net, ddevienne@gmail.com, tgl@sss.pgh.pa.us, xof@thebuild.com, adrian.klaver@aklaver.com, laurenz.albe@cybertec.at, david.g.johnston@gmail.com, m.tonies@upscene.com
  Subject: Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
  In-Reply-To: <1258414512.930087.1669990257195@connect.xfinity.com>
  References: <23DE96C56DFC404096553A22DDC5093B@MARTIJNWS> <CAKFQuwbYCk0oA3VT+ngEebBTBjdtGsVLEFOdPX2qqQJobA7rtg@mail.gmail.com> <1579912.1669908194@sss.pgh.pa.us> <CAFCRh--K2tahGetbJ_mtjiwvfFb9fF6SzjGnvbyoMKPr92FiTQ@mail.gmail.com> <c14b49a2043adafbe9589fab7af4eceb6199726c.camel@cybertec.at> <CAFCRh-8DBZdfq_r+5jX9s8XPGxrANCOuWffkBBadpRTm7VP-OA@mail.gmail.com> <bee36d64-84e3-2918-9183-6035e1e6e221@aklaver.com> <CAFCRh-_wTu8mdxurTgjVO0Z19Xs1sam0ZFQqdXAJ5eF+7NLkpA@mail.gmail.com> <0730410A-9C79-4EE2-B21B-3502445A8700@thebuild.com> <CAFCRh-_cNHc0K0zLy6s0H7kaXOwPkC0mK74aXTGA2YOqKi89FA@mail.gmail.com> <1697225.1669924271@sss.pgh.pa.us> <CAFCRh--6qhmGKy5j7RVEBWW=r3YCeRm=WogwKxEA6Nhzcc0uDg@mail.gmail.com> <1258414512.930087.1669990257195@connect.xfinity.com>

* 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