pgsql: Fix two valgrind issues in slab allocator.

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix two valgrind issues in slab allocator.
Date: 2017-04-04 21:39:26
Message-ID: E1cvWAg-0005tn-TK@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix two valgrind issues in slab allocator.

During allocation VALGRIND_MAKE_MEM_DEFINED was called with a pointer
as size. That kind of works, but makes valgrind exceedingly slow for
workloads involving the slab allocator.

Secondly there was an access to memory marked as unreachable within
SlabCheck(). Fix that too.

Author: Tomas Vondra
Discussion: https://postgr.es/m/a6543b6d-6015-99b1-63ef-3ed55a76a730@2ndquadrant.com

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/490e9a98ff964df95311e2b5a68a15f63bce0cfd

Modified Files
--------------
src/backend/utils/mmgr/slab.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2017-04-04 21:54:14 pgsql: Fix uninitialized variables in twophase.c
Previous Message Andrew Dunstan 2017-04-04 20:51:58 pgsql: Clarify documentation of to_tsvector(json(b))