Re: Out-of-bounds access (ARRAY_VS_SINGLETON) (src/backend/access/nbtree/nbtdedup.c)

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Out-of-bounds access (ARRAY_VS_SINGLETON) (src/backend/access/nbtree/nbtdedup.c)
Date: 2020-08-25 18:07:54
Message-ID: CAH2-Wzk173yY2Xz1iV09Bzx4n4-BGATrd2M1B9EydNDNY_21JQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 25, 2020 at 10:15 AM Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:
> If variable htids is accessed like array, but is a simple pointer, can be
> "This might corrupt or misinterpret adjacent memory locations."

This exact Coverity complaint has already been discussed, and marked
as a false positive on the community's Coverity installation.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-08-25 18:17:12 Re: LWLockAcquire and LockBuffer mode argument
Previous Message Robert Haas 2020-08-25 17:59:35 Re: LWLockAcquire and LockBuffer mode argument