Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index

Alexander Lakhin <exclusion@gmail.com>

From: Alexander Lakhin <exclusion@gmail.com>

To: Heikki Linnakangas <hlinnaka@iki.fi>, Tender Wang <tndrwang@gmail.com>

Cc: pgsql-bugs@lists.postgresql.org

Date: 2025-04-04T20:00:01Z

Lists: pgsql-bugs

Hello Heikki and Tender Wang,

04.04.2025 14:04, Heikki Linnakangas wrote:
> On 15/11/2024 11:10, Tender Wang wrote:
>>
>> I agree that it doesn't matter. If internal page split due to adjust key consistent with the key we're inserting.
>> The 'retry_from_parent' flag can help us get corrent downlinkoffnum.
>
> Ok, thanks for checking! Committed.
>

Thank you for working on this!

Best regards.
Alexander

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Relax assertion in finding correct GiST parent
- b92482dc3eff 13.21 landed
- a749c6f18fba 14.18 landed
- 3c0fe75c412b 15.13 landed
- 41932139882e 16.9 landed
- 6526d07948c5 17.5 landed
- 7afca7edef75 18.0 landed
Fix another bug in parent page splitting during GiST index build.
- 28d3c2ddcf91 17.0 cited