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

From Tom Lane
Subject Re: BUG #17300: Server crashes on deserializing text multirange
Date
Msg-id 2001128.1638398395@sss.pgh.pa.us
Whole thread Raw
In response to BUG #17300: Server crashes on deserializing text multirange  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17300: Server crashes on deserializing text multirange  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-bugs
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.

            regards, tom lane



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17305: to_timestamp accept dates rejected by timestamptz cast
Next
From: PG Bug reporting form
Date:
Subject: BUG #17307: Performance deviation between the multiple iterations (NOPM & TPM values).