Re: Add pg_basetype() function to obtain a DOMAIN base type - Mailing list pgsql-hackers

From jian he
Subject Re: Add pg_basetype() function to obtain a DOMAIN base type
Date
Msg-id CACJufxFX1by6p23QTSF6JDdOLVbNSdGwGPKvxvnKDhs2pyhmYw@mail.gmail.com
Whole thread Raw
In response to Re: Add pg_basetype() function to obtain a DOMAIN base type  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Add pg_basetype() function to obtain a DOMAIN base type
Re: Add pg_basetype() function to obtain a DOMAIN base type
List pgsql-hackers
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

Attachment

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Possibility to disable `ALTER SYSTEM`
Next
From: Masahiko Sawada
Date:
Subject: Re: [PoC] Improve dead tuple storage for lazy vacuum