| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Erki Eessaar <erki(dot)eessaar(at)taltech(dot)ee>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | INFORMATION_SCHEMA.routines column routine_definition does not show the source |
| Date: | 2024-09-18 05:42:53 |
| Message-ID: | CAKFQuwYjULC9cUgC_whSsJZ0a4=7naNLMcws1_TJPHSOLFw57Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Ping again as a Reddit poster just pointed this out.
On Thursday, December 1, 2022, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
> > We could partially fix that by teaching psql to also recognize
> > "BEGIN" as the start of the function body.
>
> Looks like we need "RETURN " too, so more or less as attached.
>
> (I didn't bother with a test case yet. \sf wouldn't be too
> hard to exercise, but I wonder how we could test \ef portably.)
>
>
>
Not sure I bring much to patch review here; but is the plan to commit this
first then update information_schema or do both in one go?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-09-18 05:45:31 | Re: Leader backend hang on IPC/ParallelFinish when LWLock held at parallel query start |
| Previous Message | Noah Misch | 2024-09-18 05:30:26 | Re: Leader backend hang on IPC/ParallelFinish when LWLock held at parallel query start |