Message-ID: <0e8907d8a0cb19b64d732ec7b44f8eb669b54075.camel@cybertec.at>
Subject: Re: BUG #19098: Can't create unique gist index, where pg_indexes
 says that WITHOUT OVERLAPS does exacly that
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Paul A Jungwirth <pj@illuminatedcomputing.com>, Tom Lane
 <tgl@sss.pgh.pa.us>
Cc: n.bartek3762@gmail.com, pgsql-bugs@lists.postgresql.org, Peter
 Eisentraut	 <peter@eisentraut.org>, Matthias van de Meent
 <boekewurm+postgres@gmail.com>
Date: Thu, 30 Oct 2025 11:30:13 +0100
In-Reply-To: 
 <CA+renyV3dxf8TSEG7C0vpwwFDr67KF=FGCTZ8ZrXWxOK-T1vfw@mail.gmail.com>
References: <19098-7f8deb5093c13da2@postgresql.org>
	 <11e73b0d2d89476fb04e6055a80638f776bb6f18.camel@cybertec.at>
	 <2748212.1761750444@sss.pgh.pa.us> <2750966.1761751813@sss.pgh.pa.us>
	 <CA+renyV3dxf8TSEG7C0vpwwFDr67KF=FGCTZ8ZrXWxOK-T1vfw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/0e8907d8a0cb19b64d732ec7b44f8eb669b54075.camel%40cybertec.at>
Precedence: bulk

On Wed, 2025-10-29 at 11:51 -0700, Paul A Jungwirth wrote:
> So here is a proposed sequence of work:
>=20
> - Add an opclass_parameter so you can say without_overlaps =3D true.
> Only the last column of the index allows that (at least for now), and
> there must be an overlaps operator.
> - If an index has that property, enforce the exclusion constraint
> rules and forbid empty ranges/multiranges.
> - Update pg_get_indexdef to output the right syntax to create an
> independent temporal index.
> - Allow USING INDEX for WITHOUT OVERLAPS. It must be a temporal index.
> - Support can_unique in GiST indexes using CompareType. (Perhaps this
> is of low practical value, but the discrepancies bug me.)
> - Add can_temporal to index AMs. Make GiST report true. Check this
> property instead of hard-coding GiST in our WITHOUT OVERLAPS code.
> - Support reindexing these indexes concurrently. (I'm not signing up
> for this just yet, but maybe someday.)
> - Support creating these indexes concurrently. (I'm not signing up for
> this just yet, but maybe someday.)

That's perhaps a good way for the future, but the cat is already out
of the bag.  Do you have any ideas what to do about v18?

Yours,
Laurenz Albe