Re: BUG #17874: Incorrect memory access at gistBuildCallback

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, kyzevan23(at)mail(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17874: Incorrect memory access at gistBuildCallback
Date: 2023-03-29 11:47:12
Message-ID: 3802070.1680090432@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> On 29 Mar 2023, at 12:00, Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
>> That issue was reported already as bug #16329:
>> https://www.postgresql.org/message-id/flat/16329-7a6aa9b6fa1118a1%40postgresql.org
>> Maybe it's worth to register the fix proposed there for the next commitfest...

> Summarizing that thread and registering the proposed patch for the next
> commitfest seems like the right thing to do.

Yeah. We did fix the lack of test coverage that much of that thread
was about, but it seems like we forgot the original bug (which I
guess indicates that the coverage is still inadequate, since the
valgrind buildfarm animals haven't noticed it...)

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-03-29 12:33:37 Re: BUG #17876: Function width_bucket() for float8 input returns value out of range
Previous Message Daniel Gustafsson 2023-03-29 10:11:09 Re: BUG #17874: Incorrect memory access at gistBuildCallback