Re: psql: add \create_function command
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: walther@technowledgy.de, Steve Chavez <steve@supabase.io>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-01-26T20:18:47Z
Lists: pgsql-hackers
pá 26. 1. 2024 v 21:17 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal: > Pavel Stehule <pavel.stehule@gmail.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 >
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Combine FSM updates for prune and no-prune cases.
- 5eafacd2797d 17.0 cited