Re: pgsql: Avoid valgrind complaint about write() of uninitalized bytes. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pgsql: Avoid valgrind complaint about write() of uninitalized bytes.
Date
Msg-id CA+TgmoZ7AKrzOVO7L3opSGyEEj07e9YU+20O=58UsmXjYWTZ9A@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Avoid valgrind complaint about write() of uninitalized bytes.  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: pgsql: Avoid valgrind complaint about write() of uninitalized bytes.
Re: pgsql: Avoid valgrind complaint about write() of uninitalized bytes.
List pgsql-hackers
On Wed, Feb 21, 2018 at 3:18 PM, Peter Geoghegan <pg@bowt.ie> wrote:
> On Wed, Feb 21, 2018 at 10:55 AM, Peter Geoghegan <pg@bowt.ie> wrote:
>> Sure, but it looks like it has the exact same underlying cause to the
>> LogicalTapeFreeze() issue. It shouldn't be very hard to write an
>> equivalent patch for LogicalTapeRewindForRead() -- I pointed out that
>> this could happen there instead before the first patch went in, in
>> fact. My mistake was to imagine that that could never happen during
>> the regression tests.
>
> Attached patch does this. I cannot recreate this issue locally, but
> this should still fix it on skink.

Committed.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [doc fix] Correct calculation of vm.nr_hugepages
Next
From: Robert Haas
Date:
Subject: Re: PlaceHolderVars in pushed down child-join cause error