| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Protecting allocator headers with Valgrind |
| Date: | 2023-04-12 01:59:22 |
| Message-ID: | CAMbWs48th=nGAznZnEkNGy_WzADsUVHLYSTg5xbnzgQ4MpM3yg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 11, 2023 at 9:28 PM David Rowley <dgrowleyml(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yurii Rashkovskii | 2023-04-12 02:17:29 | Re: [PATCH] Allow Postgres to pick an unused port to listen |
| Previous Message | Greg Stark | 2023-04-12 01:48:12 | Re: pg_init_privs corruption. |