Re: Add pg_basetype() function to obtain a DOMAIN base type
jian he <jian.universality@gmail.com>
From: jian he <jian.universality@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alexander Korotkov <aekorotkov@gmail.com>,
Tomas Vondra <tomas.vondra@enterprisedb.com>, John Naylor <johncnaylorls@gmail.com>, Steve Chavez <steve@supabase.io>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-03-21T02:34:36Z
Lists: pgsql-hackers
Attachments
- v5-0001-Add-pg_basetype-regtype-function-to-return-the-ba.patch (application/x-patch) patch v5-0001
On Mon, Mar 18, 2024 at 11:43 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Alexander Korotkov <aekorotkov@gmail.com> writes:
> > On Mon, Mar 18, 2024 at 2:01 AM jian he <jian.universality@gmail.com> wrote:
> >> `
> >> Datum
> >> pg_basetype(PG_FUNCTION_ARGS)
> >> {
> >> Oid oid;
> >>
> >> oid = get_fn_expr_argtype(fcinfo->flinfo, 0);
> >> PG_RETURN_OID(getBaseType(oid));
> >> }
> >> `
>
> > Looks good to me. But should it be named pg_basetypeof()?
>
> I still don't like this approach. It forces the function to be
> used in a particular way that's highly redundant with pg_typeof.
> I think we'd be better off with
>
> pg_basetype(PG_FUNCTION_ARGS)
> {
> Oid typid = PG_GETARG_OID(0);
>
> PG_RETURN_OID(getBaseType(typid));
> }
>
> The use-case that the other definition handles would be implemented
> like
>
> pg_basetype(pg_typeof(expression))
>
trying to do it this way.
not sure the following error message is expected.
SELECT pg_basetype(-1);
ERROR: cache lookup failed for type 4294967295
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