Re: BUG #17300: Server crashes on deserializing text multirange - Mailing list pgsql-bugs

From Alexander Korotkov
Subject Re: BUG #17300: Server crashes on deserializing text multirange
Date
Msg-id CAPpHfdtrb9uc804wiKoqSkgt22++YFgRuTUE8u9gS1jhxSAa5w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17300: Server crashes on deserializing text multirange  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #17300: Server crashes on deserializing text multirange  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-bugs
On Thu, Dec 2, 2021 at 1:39 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> PG Bug reporting form <noreply@postgresql.org> writes:
> > The following query:
>
> > select ('[\"\\\\\",\"\\\\' || repeat('a', 200) ||
> > '\"]')::textrange::textmultirange
>
> > leads to the server crash with the following stacktrace:
>
> I think the problem here is that the range bound values inside the
> multirange are supposed to be aligned (at least, write_multirange_data
> thinks so) but multirange_get_range isn't accounting for the alignment
> padding between the two values it extracts.  In this example that
> causes it to extract an insane length for the second value.
>
> If so, this would indicate extremely slipshod testing of the multirange
> stuff, because the breakage is necessarily reached by multirange_out.

Sorry for the delay.  I'm going to fix this in the next couple of days.

------
Regards,
Alexander Korotkov



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17323: test_config_settings during postgres initialization does not read the parameter huge_pages
Next
From: Min Zhang XX
Date:
Subject: RE: BUG #17323: test_config_settings during postgres initialization does not read the parameter huge_pages