From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | walther(at)technowledgy(dot)de, Steve Chavez <steve(at)supabase(dot)io>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql: add \create_function command |
Date: | 2024-01-26 20:18:47 |
Message-ID: | CAFj8pRCp=HNC7oNB33KDYcvU0wjBVp2z3HHoU16Ej_uDaBy+qg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
pá 26. 1. 2024 v 21:17 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > I don't know, maybe I have a problem with the described use case. I
> cannot
> > imagine holding the body and head of PL routines in different places and
> I
> > don't understand the necessity to join it.
>
> It seems a little weird to me too, and I would vote against accepting
> \create_function as described because I think too few people would
> want to use it. However, the idea of an easy way to pull in a file
> and convert it to a SQL literal seems like it has many applications.
>
+1
Pavel
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adam S | 2024-01-26 20:23:43 | Re: psql: add \create_function command |
Previous Message | Tom Lane | 2024-01-26 20:17:46 | Re: psql: add \create_function command |