Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
Date
Msg-id CAH2-WzkTvnAfAMLfo5Rs+xn0Jnhf4riRt0Q6gu=_H1NO1XJJxQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
List pgsql-bugs
On Wed, Feb 16, 2022 at 4:16 PM Tomas Vondra
<tomas.vondra@enterprisedb.com> wrote:
> test=# SELECT * FROM gist_page_items(get_raw_page('path_gist_idx', 0),
> 'path_gist_idx');

Maybe this is obvious, but just in case: gist_page_items is *very*
trusting here. It's necessary to use gist_page_items_bytea() if you're
not 100% sure about the index definition for the index page you
provide. The fact that you can display the contents of each tuple
using the underlying type's own output function is very handy. But
potentially hazardous.

-- 
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
Next
From: Tomas Vondra
Date:
Subject: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade