Re: BUG #15217: Valgrind - writing uninitialised byte(s) in FileWrite

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: exclusion(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15217: Valgrind - writing uninitialised byte(s) in FileWrite
Date: 2018-05-30 05:54:52
Message-ID: CAH2-Wzk-=Omu4eoTYeYV42uRx+Y6DBjE84=G-fMBkHHVf6wVPw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, May 29, 2018 at 9:02 PM, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> Is this something that needs further investigation (and fix) or it just
> looks like a false positive (and should be added to valgrind.supp)?

This looks like the same harmless warning that we suppressed for
parallel sort in Postgres 11 (see commits 9fafa413ac6 and
de6428afe13). This happens to be a serial sort in Postgres 10, but the
fact that it's still possible there isn't surprising.

What's your work_mem setting? Can you show EXPLAIN ANALYZE output for the query?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Lakhin 2018-05-30 06:35:25 Re: BUG #15217: Valgrind - writing uninitialised byte(s) in FileWrite
Previous Message PG Bug reporting form 2018-05-30 04:02:50 BUG #15217: Valgrind - writing uninitialised byte(s) in FileWrite