Re: BUG #17888: Incorrect memory access in gist__int_ops for an input array with many elements - Mailing list pgsql-bugs

From Alexander Lakhin
Subject Re: BUG #17888: Incorrect memory access in gist__int_ops for an input array with many elements
Date
Msg-id 02538745-31d0-1f78-f994-86ca794f0466@gmail.com
Whole thread Raw
In response to Re: BUG #17888: Incorrect memory access in gist__int_ops for an input array with many elements  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Hi Michael,

15.06.2023 07:53, Michael Paquier wrote:
> I have spent some time on that today, and applied what has been
> suggested to restrict the usage of this operator when inserting data
> for a leaf page, so as the decompression does not get crazy when
> retrieving the contents of the leaf pages.

Thank you for paying attention to it!
I closed https://commitfest.postgresql.org/43/4280/ as committed.

The confusing message I noted previously:
ERROR:  index row size 8040 exceeds maximum 8152 for index "test_idx"
is not emitted now, although I think it still can be produced for some
other gist indexes. But that's a matter for another day, I suppose.

Best regards,
Alexander



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17978: Unexpected error: "wrong varnullingrels (b) (expected (b 5)) for Var 6/2" triggered by JOIN
Next
From: Tom Lane
Date:
Subject: Re: BUG #17977: PorstGreSQL in a jail crashes randomly with Signal 10 bus error