| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
| Cc: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extract numeric filed in JSONB more effectively |
| Date: | 2023-08-18 05:02:55 |
| Message-ID: | CACJufxHv+Yo+ivq5u+cjo9Fa=SyfvA-V4CLePuS0JgLiC-yCBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 18, 2023 at 10:55 AM Chapman Flack <chap(at)anastigmatix(dot)net> wrote:
>
>
> Again, all of that complication stems from the choice to use the
> anyelement return type and rely on polymorphic type resolution
> to figure the oid out, when we already have the oid to begin with
> and the oid is all we want.
>
you want jsonb_object_field_type(internal, jsonb, text)? because on
sql level, it's safe.
The return data type is determined when we are in jsonb_cast_support.
we just need to pass the {return data type} information to the next
function: jsonb_object_field_type.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-08-18 05:07:34 | Re: logical decoding and replication of sequences, take 2 |
| Previous Message | Dilip Kumar | 2023-08-18 04:42:00 | Re: New WAL record to detect the checkpoint redo location |