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 CAPpHfduJEJbeRGm-VgeyPAzNzC6oc8u+WNqfcZgWnXPUo6F6Dg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17847: Unaligned memory access in ltree_gist  (Pavel Borisov <pashkin.elfe@gmail.com>)
Responses Re: BUG #17847: Unaligned memory access in ltree_gist
List pgsql-bugs
Hi, Pavel!

On Tue, Apr 18, 2023 at 1:34 PM Pavel Borisov <pashkin.elfe@gmail.com> wrote:
> I've looked into the patch v2 and there is a difference in DETAIL text
> for the cases:
>
> (1)
>  create index tstidx on ltreetest using gist (t gist_ltree_ops(siglen=2025));
> +ERROR:  siglen value must be integer-aligned
> +DETAIL:  Valid values are int-aligned positive integers up to 2024.
>
> (2)
> +create index tstidx on ltreetest using gist (t gist_ltree_ops(siglen=2028));
> +ERROR:  value 2028 out of bounds for option "siglen"
> +DETAIL:  Valid values are between "4" and "2024"
>
> Could we stick to the DETAIL like in (2) for both cases?

Within ltree we don't have control over error messages, which GUC code
emits about min/max boundaries violation (for sure, we're not going to
patch GUC code in this fix).  So the only thing I can do to match
these two DETAIL is to make both of them 'Valid values are between "4"
and "2024"'.  However, this message would be kind of irrelevant for
"siglen value must be integer-aligned" error.  It's strange for me
when an error mentions alignment, but DETAIL does not.

Do you think we can just remove the DETAIL for "siglen value must be
integer-aligned" error?

------
Regards,
Alexander Korotkov



pgsql-bugs by date:

Previous
From: Pavel Borisov
Date:
Subject: Re: BUG #17847: Unaligned memory access in ltree_gist
Next
From: Pavel Borisov
Date:
Subject: Re: BUG #17847: Unaligned memory access in ltree_gist