Re: Create unique GiST indexes - Mailing list pgsql-hackers

From Paul A Jungwirth
Subject Re: Create unique GiST indexes
Date
Msg-id CA+renyWWNOBzmfFEEaJL3zw8RRjib3MNDxuhvjf+0b4Dp9eT4g@mail.gmail.com
Whole thread Raw
In response to Re: Create unique GiST indexes  (Paul A Jungwirth <pj@illuminatedcomputing.com>)
List pgsql-hackers
On Fri, Jan 2, 2026 at 10:39 AM Paul A Jungwirth
<pj@illuminatedcomputing.com> wrote:
>
> This is the missing MVCC functionality I mentioned when I posted the
> patch. It's the next thing on my list to work on. As I said the patch
> is not really done. But it took longer than I expected to send a reply
> to Matthias, and I wanted to post something before the commitfest
> deadline. And I thought I at least had enough to get feedback on the
> overall approach.
>
> I think your example here would make a great isolation test though.
> I'll incorporate that into future work, or please feel free to write
> it yourself and share if you like.

I realized my approach to this patch is just wrong, because I'm only
searching one index leaf page for conflicts (whichever one the insert
lands on), and they might be in different pages, due to changes in
penalty, splits, and maybe other reasons. I've been working on a
different approach, but I don't have something ready to send in yet.
I've updated the commitfest status to Waiting on Author.

Yours,

--
Paul              ~{:-)
pj@illuminatedcomputing.com



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
Next
From: Heikki Linnakangas
Date:
Subject: Re: Better shared data structure management and resizable shared data structures