Re: Protecting allocator headers with Valgrind - Mailing list pgsql-hackers

From Richard Guo
Subject Re: Protecting allocator headers with Valgrind
Date
Msg-id CAMbWs48th=nGAznZnEkNGy_WzADsUVHLYSTg5xbnzgQ4MpM3yg@mail.gmail.com
Whole thread Raw
In response to Protecting allocator headers with Valgrind  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers

On Tue, Apr 11, 2023 at 9:28 PM David Rowley <dgrowleyml@gmail.com> wrote:
Over on [1], Tom mentioned that we might want to rethink the decision
to not protect chunk headers with Valgrind.  That thread fixed a bug
that was accessing array element -1, which effectively was reading the
MemoryChunk at the start of the allocated chunk as an array element.

Seems the link to the original thread is not pasted.  Here it is.

[1] https://www.postgresql.org/message-id/1650235.1672694719%40sss.pgh.pa.us

Thanks
Richard

pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: pg_init_privs corruption.
Next
From: Yurii Rashkovskii
Date:
Subject: Re: [PATCH] Allow Postgres to pick an unused port to listen