Re: BUG #17300: Server crashes on deserializing text multirange
От | Alexander Korotkov |
---|---|
Тема | Re: BUG #17300: Server crashes on deserializing text multirange |
Дата | |
Msg-id | CAPpHfdtPFbiUtKq7gB1=mMQZz-RaXnZ3=sEtdOVKByO0E58s=A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #17300: Server crashes on deserializing text multirange (Alexander Korotkov <aekorotkov@gmail.com>) |
Ответы |
Re: BUG #17300: Server crashes on deserializing text multirange
|
Список | pgsql-bugs |
On Mon, Dec 6, 2021 at 10:39 PM Alexander Korotkov <aekorotkov@gmail.com> wrote: > 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. The proposed patch fixes the patch (and adds some minimal testing for it). I'm going to push it if no objections (backpatch to v14). ------ Regards, Alexander Korotkov
Вложения
В списке pgsql-bugs по дате отправления: