Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Wed, 03 Jan 2024 18:05:47 -0500
Message-Id: <CY5G4TAMVX32.23TH6LFF93ATZ@nmfay.com>
Cc: "PostgreSQL Hackers" <pgsql-hackers@lists.postgresql.org>
Subject: Re: add function argument names to regex* functions.
From: "Dian Fay" <di@nmfay.com>
To: "Jim Nasby" <jim.nasby@gmail.com>, "jian he"
 <jian.universality@gmail.com>, "Peter Eisentraut" <peter@eisentraut.org>
References: 
 <CACJufxG3NFKKsh6x4fRLv8h3V-HvN4W5dA=zNKMxsNcDwOKang@mail.gmail.com>
 <b550243f-1bd2-4119-82e9-0f0abccc6434@eisentraut.org>
 <CACJufxHeyc34PMx6OnWb-xoaMtj1Yoax1rM+71zkwCynvmVwdg@mail.gmail.com>
 <CY3KI01TXYMD.3Q41WQ6U0NFEO@nmfay.com>
 <0eb3a5d7-75d8-4da5-9c88-a93deccdaa03@gmail.com>
In-Reply-To: <0eb3a5d7-75d8-4da5-9c88-a93deccdaa03@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/CY5G4TAMVX32.23TH6LFF93ATZ%40nmfay.com>
Precedence: bulk

> > Another possibility is `index`, which is relatively short and not a
> > reserved keyword ^1. `position` is not as precise but would avoid the
> > conceptual overloading of ordinary indices.
>
> I'm not a fan of "index" since that leaves the question of
> whether it's 0 or 1 based. "Position" is a bit better, but I think
> Jian's suggestion of "occurance" is best.

We do have precedent for one-based `index` in Postgres: array types are
1-indexed by default! "Occurrence" removes that ambiguity but it's long
and easy to misspell (I looked it up after typing it just now and it
_still_ feels off).

How's "instance"?