| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | Alban Hertroys <haramrae(at)gmail(dot)com> |
| Cc: | DAVID ROTH <adaptron(at)comcast(dot)net>, Dominique Devienne <ddevienne(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christophe Pettus <xof(at)thebuild(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "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: | Aw: Re: Stored procedure code no longer stored in v14 and v15, changed behaviour |
| Date: | 2022-12-03 19:55:47 |
| Message-ID: | trinity-14b76257-6780-433b-8624-c2be32f0d603-1670097346999@3c-app-gmx-bap57 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> You would need to wrap the function creation calls into some automation to generate and store those diffs, comparing it back, etc, but that may be doable. I would also generate new diffs right after major version updates of the database (a before and after of the output of pg_get_functiondef, applied to the stored diff?).
I wonder whether that would tie the sanity check to a particular PG version.
I mean, pg_get_functiondef output being a server runtime artifact it might
well change between server versions, no ?
Best,
Karsten
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jacktby@gmail.com | 2022-12-04 05:32:23 | How to repair my plan modify error? |
| Previous Message | David Rowley | 2022-12-03 19:06:46 | Re: sort performance better with little memory than big memory |