Re: [PATCH] regexp_positions ( string text, pattern text, flags text ) → setof int4range[]

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Joel Jacobson <joel(at)compiler(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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>, Gilles Darold <gilles(at)darold(dot)net>
Subject: Re: [PATCH] regexp_positions ( string text, pattern text, flags text ) → setof int4range[]
Date: 2021-03-09 12:16:10
Message-ID: CAFj8pRApC47ZskoxJ54ELdcY3YPE07vrTLhshh42Ru6DLqxKkw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

út 9. 3. 2021 v 11:32 odesílatel Joel Jacobson <joel(at)compiler(dot)org> napsal:

> On Thu, Mar 4, 2021, at 16:40, Tom Lane wrote:
>
> My experience with working with parallel arrays in SQL has been unpleasant.
>
>
> Could you please give an example on such an unpleasant experience?
>

it was more complex application with 3D data of some points in 2D array.
Everywhere was a[d, 0], a[d, 1], a[d, 2], instead a[d] or instead a[d].x,
...

> I can see a problem if the arrays could possibly have difference
> dimensionality/cardinality,
> but regexp_positions() could guarantee they won't, so I don't see a
> problem here,
> but there is probably something I'm missing here?
>

I think so the functions based on arrays can work, why not. But the
semantic is lost.

> /Joel
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-03-09 12:27:48 Re: SQL-standard function body
Previous Message Thomas Munro 2021-03-09 12:11:59 Outdated comments about proc->sem in lwlock.c