Re: psql: add \create_function command

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: walther(at)technowledgy(dot)de
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, 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 19:52:05
Message-ID: 1026681.1706298725@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

walther(at)technowledgy(dot)de writes:
> Pavel Stehule:
>> looks a little bit obscure - why do you need to do it from psql? And how
>> frequently do you do it?

> I store all my SQL code in git and use "psql -e" to "bundle" it into an
> extension, which is then deployed to production.

> The code is spread over many files, which include other files via \ir.

That reminds me: if we do either \file_read or :{file}, we should
define relative paths as working like \ir, that is it's relative
to the current script's directory when we're reading from a script.
This is almost always the behavior you want, and the principal
functional problem with the `cat ...` solution is that it doesn't
work that way.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tristen Raab 2024-01-26 19:56:37 Re: Add minimal C example and SQL registration example for custom table access methods.
Previous Message Pavel Stehule 2024-01-26 19:50:22 Re: psql: add \create_function command