From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_get_functiondef(), trailing spaces and + sign |
Date: | 2023-02-27 19:38:33 |
Message-ID: | 99e9267e-a8a5-7c66-e708-35dd6e9db473@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/27/23 11:34 AM, Ron wrote:
> Is there any direct way in Postgresql to get rid of the frankly
> anti-useful junk at the end of each line (which also infects
> pg_stat_activity.query), or must I resort to sed post-processing?
\pset format unaligned
>
>
> test=# select pg_get_functiondef(oid)
> test-# from pg_proc
> test-# where proname = 'foo';
> pg_get_functiondef
> ----------------------------------------------------
> CREATE OR REPLACE FUNCTION public.foo(bar integer)+
> RETURNS double precision +
> LANGUAGE plpgsql +
> AS $function$ +
> begin +
> return bar * 1.0; +
> end; +
> $function$ +
>
> (1 row)
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-02-27 19:40:08 | Re: pg_get_functiondef(), trailing spaces and + sign |
Previous Message | Ron | 2023-02-27 19:34:30 | pg_get_functiondef(), trailing spaces and + sign |