From: Alexander Lakhin <exclusion@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org, Alexander Korotkov <aekorotkov@gmail.com>
Subject: Re: BUG #17847: Unaligned memory access in ltree_gist
Date: Sat, 18 Mar 2023 10:00:01 +0300
Message-ID: <f9591c60-b241-5f03-711d-171ded31650a@gmail.com> (raw)
In-Reply-To: <3966266.1678995315@sss.pgh.pa.us>
References: <17847-171232970bea406b@postgresql.org>
<3966266.1678995315@sss.pgh.pa.us>
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)
Best regards,
Alexander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: exclusion@gmail.com, tgl@sss.pgh.pa.us, aekorotkov@gmail.com
Subject: Re: BUG #17847: Unaligned memory access in ltree_gist
In-Reply-To: <f9591c60-b241-5f03-711d-171ded31650a@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox