| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joel Jacobson" <joel(at)compiler(dot)org> |
| Cc: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Mark Dilger" <mark(dot)dilger(at)enterprisedb(dot)com>, "Postgres hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Andreas Karlsson" <andreas(at)proxel(dot)se>, "David Fetter" <david(at)fetter(dot)org> |
| Subject: | Re: Re: [PATCH] regexp_positions ( string text, pattern text, flags text ) → setof int4range[] |
| Date: | 2021-03-09 16:20:20 |
| Message-ID: | 2032516.1615306820@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joel Jacobson" <joel(at)compiler(dot)org> writes:
> On Tue, Mar 9, 2021, at 10:18, Pavel Stehule wrote:
>> you can do unnest(array1, array2, ...)
> Right, I had forgotten about that variant.
> But isn't this a bit surprising then:
> ...
> Should there be an entry there showing the VARIADIC anyelement version as well?
No, because there's no such pg_proc entry. Multi-argument UNNEST is
special-cased by the parser, cf transformRangeFunction().
(Which is something I'd momentarily forgotten. Forget my suggestion
that we could define unnest(anyarray, int) ... it has to be another
name.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2021-03-09 16:21:44 | Re: Lowering the ever-growing heap->pd_lower |
| Previous Message | Joel Jacobson | 2021-03-09 16:11:14 | Re: [PATCH] pg_permissions |