Re: BUG #17847: Unaligned memory access in ltree_gist - Mailing list pgsql-bugs

From Alexander Korotkov
Subject Re: BUG #17847: Unaligned memory access in ltree_gist
Date
Msg-id CAPpHfdt4bXSjXqsPZwQcTXVvzpPwYxPLGR=9ZDiQ=6vaSkYF1A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17847: Unaligned memory access in ltree_gist  (Alexander Lakhin <exclusion@gmail.com>)
List pgsql-bugs
On Sat, Mar 18, 2023 at 10:00 AM Alexander Lakhin <exclusion@gmail.com> wrote:
> 16.03.2023 22:35, Tom Lane wrote:
>
> I wonder which other opclasses besides ltree have the same issue.
>
>
> I found no other similar places: siglen is also accepted by opclasses
> gist__intbig_ops, gist_hstore_ops, gist_trgm_ops, tsvector_ops,
> which implementations use functions
> _intbig_alloc, ghstore_alloc, gtrgm_alloc, gtsvector_alloc,
> and none of them adds siglen to a pointer.
> Quick testing confirms that.
>
> (gist__ltree_ops uses ltree_gist_alloc(), but the problematic branch
> "if (left) ..." not reached for gist__ltree_ops)

Yep, ltree seems the only place storing aligned value *after*
signature.  Thank you for validating this.

------
Regards,
Alexander Korotkov



pgsql-bugs by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: BUG #17847: Unaligned memory access in ltree_gist
Next
From: Tom Lane
Date:
Subject: Re: BUG #17853: COLLATE does not work with numeric column references in ORDER BY