pgsql: Avoid access to uninitialized memory in shared tidbitmap iterati

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid access to uninitialized memory in shared tidbitmap iterati
Date: 2017-03-16 19:10:46
Message-ID: E1coanO-0005lT-JD@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Avoid access to uninitialized memory in shared tidbitmap iteration.

Primarily, this didn't work correctly when the tidbitmap ended up
empty.

Dilip Kumar, per a report from Emre Hasegeli

Discussion: http://postgr.es/m/CAFiTN-ujHFKb8WSLhK54rfqQT3r2yiPQOyeBrCDsA4p9Fwp_jw@mail.gmail.com

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/80824ddda30154d56c9f40fe47dd1900d44ced32

Modified Files
--------------
src/backend/nodes/tidbitmap.c | 51 ++++++++++++++++++++++++++++---------------
1 file changed, 33 insertions(+), 18 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Gierth 2017-03-16 22:39:31 pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in
Previous Message Robert Haas 2017-03-16 19:05:07 pgsql: Add pg_ls_logdir() and pg_ls_waldir() functions.