Re: Add pg_basetype() function to obtain a DOMAIN base type
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: jian he <jian.universality@gmail.com>,
John Naylor <johncnaylorls@gmail.com>,
Alexander Korotkov <aekorotkov@gmail.com>,
Steve Chavez <steve@supabase.io>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-02-18T00:47:38Z
Lists: pgsql-hackers
Tomas Vondra <tomas.vondra@enterprisedb.com> writes: > On 2/17/24 20:20, Tom Lane wrote: >> I don't have an immediate proposal for exactly what to call such a >> function, but naming it by analogy to pg_typeof would be questionable. > Are you objecting to the pg_basetypeof() name, or just to it accepting > "any" argument? I think pg_basetypeof(regtype) would work ... I'm not sure. "pg_basetypeof" seems like it invites confusion with "pg_typeof", but I don't really have a better idea. Perhaps "pg_baseofdomain(regtype)"? I'm not especially thrilled with that, either. Also, just to be clear, we intend this to drill down to the bottom non-domain type, right? Do we need a second function that goes down only one level? I'm inclined to say "no", mainly because (1) that would complicate the naming situation even more, and (2) that use-case is pretty easy to handle with a sub-select. 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 →
-
Add pg_basetype() function to extract a domain's base type.
- b154d8a6d0e5 17.0 landed