pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dominique Devienne <ddevienne@gmail.com>
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: Thu, 01 Dec 2022 14:51:11 -0500
Message-ID: <1697225.1669924271@sss.pgh.pa.us> (raw)
In-Reply-To: <CAFCRh-_cNHc0K0zLy6s0H7kaXOwPkC0mK74aXTGA2YOqKi89FA@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>

Dominique Devienne <ddevienne@gmail.com> writes:
> On Thu, Dec 1, 2022 at 8:09 PM Christophe Pettus <xof@thebuild.com> wrote:
>> 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.

> That's not the point. If a DBA updates one of our triggers or proc or
> whatever else,
> the recorded info in a custom table won't be affected. We are diff'ing
> the server-side
> schema, against the expected in-memory model of the physical model.

> Thus the dictionaries are the only source of truth we can trust for
> the current state of the schema.
> And beside minor syntactic differences, and some more troublesome
> object-name rewrites, this is
> exactly what we want. The system itself needs to preserve the original
> DDL IMHO. --DD

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

			regards, tom lane





view thread (37+ messages)  latest in thread

Message-ID: <1697225.1669924271@sss.pgh.pa.us>
Permalink:  ../1697225.1669924271@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1697225.1669924271@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, ddevienne@gmail.com, 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: <1697225.1669924271@sss.pgh.pa.us>
  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>

* 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