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: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] regexp_positions ( string text, pattern text, flags text ) → setof int4range[]
Date: 2021-03-05 12:57:43
Message-ID: CAFj8pRB_591r9swPbJVqQUG3jC49LADCJsin_BZ1r13FCj0oaA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

pá 5. 3. 2021 v 13:44 odesílatel Joel Jacobson <joel(at)compiler(dot)org> napsal:

> Idea #5:
>
> Allow disabling canonicalization via optional parameter to range
> constructor functions.
>

I think so rules describing ranges and multirages are long enough, so
increasing functionality doesn't look like a practical idea.

I prefere special simple composite type like you described in the previous
email (start, stop) or (start, length). It can be used more times when
using range or multi range is not practical.

The composite types are more natural for this purpose than 2D arrays.

Regards

Pavel

> This would then allow using the range type,
> to create inclusive/inclusive integer ranges,
> where lower() and upper() would return what you expect.
>
> /Joel
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Nancarrow 2021-03-05 13:04:36 Re: Parallel INSERT (INTO ... SELECT ...)
Previous Message k.jamison@fujitsu.com 2021-03-05 12:56:25 RE: libpq debug log