| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dian Fay <dian(dot)m(dot)fay(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Vik Fearing <vikreykja(at)gmail(dot)com> |
| Subject: | Re: TRIM_ARRAY |
| Date: | 2021-03-01 23:53:41 |
| Message-ID: | 865850.1614642821@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dian Fay <dian(dot)m(dot)fay(at)gmail(dot)com> writes:
> This basically does what it says, and the code looks good. The
> documentation is out of alphabetical order (trim_array should appear
> under cardinality rather than over)) but good otherwise. I was able to
> "break" the function with an untyped null in psql:
> select trim_array(null, 2);
> ERROR: could not determine polymorphic type because input has type unknown
That's a generic parser behavior for polymorphic functions, not something
this particular function could or should dodge.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dian M Fay | 2021-03-02 00:02:50 | Re: TRIM_ARRAY |
| Previous Message | Vik Fearing | 2021-03-01 23:53:04 | Re: TRIM_ARRAY |