| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held) |
| Date: | 2020-07-19 02:45:42 |
| Message-ID: | CAH2-WzmF0ECfd04uy6ONBBE6RYfTXB3=wxzO36C4rKrWygvKsQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jul 18, 2020 at 7:36 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wonder whether skink's failure today is due to this change:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2020-07-18%2018%3A01%3A10
That seems extremely likely. I think that I need to do something like
what you see in the attached.
Anyway, I'll take care of it tomorrow. Sorry for missing it before my commit.
--
Peter Geoghegan
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Mark-buffers-as-defined-to-Valgrind-consistently.patch | application/octet-stream | 1.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2020-07-19 03:03:26 | Re: [PATCH] Keeps tracking the uniqueness with UniqueKey |
| Previous Message | Tom Lane | 2020-07-19 02:36:36 | Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held) |