From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Alexander Lakhin <exclusion@gmail.com>
Cc: kyzevan23@mail.ru
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17874: Incorrect memory access at gistBuildCallback
Date: Wed, 29 Mar 2023 07:47:12 -0400
Message-ID: <3802070.1680090432@sss.pgh.pa.us> (raw)
In-Reply-To: <E718477B-9693-4BAF-B4E9-8FE36C3EB986@yesql.se>
References: <17874-63ca6c7ce42d2103@postgresql.org>
<6341c61d-e6cd-bc68-8a8b-8b307b6f9359@gmail.com>
<E718477B-9693-4BAF-B4E9-8FE36C3EB986@yesql.se>
Daniel Gustafsson <daniel@yesql.se> writes:
>> On 29 Mar 2023, at 12:00, Alexander Lakhin <exclusion@gmail.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, daniel@yesql.se, exclusion@gmail.com, kyzevan23@mail.ru, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17874: Incorrect memory access at gistBuildCallback
In-Reply-To: <3802070.1680090432@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox