pgsql: Fix the initialization of atomic variables introduced by the

From: Amit Kapila <akapila(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix the initialization of atomic variables introduced by the
Date: 2018-11-13 05:40:55
Message-ID: E1gMRRX-0000Jt-Gg@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix the initialization of atomic variables introduced by the
group clearing mechanism.

Commits 0e141c0fbb and baaf272ac9 introduced initialization of atomic
variables in InitProcess which means that it's not safe to look at those
for backends that aren't currently in use. Fix that by initializing them
during postmaster startup.

Reported-by: Andres Freund
Author: Amit Kapila
Backpatch-through: 9.6
Discussion: https://postgr.es/m/20181027104138.qmbbelopvy7cw2qv@alap3.anarazel.de

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/d4d9f21b64d4290cc6695bcd93a8e4c5fc16badf

Modified Files
--------------
src/backend/storage/lmgr/proc.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2018-11-13 05:44:35 Re: pgsql: Fix handling of HBA ldapserver with multiple hostnames.
Previous Message Tom Lane 2018-11-13 05:37:11 Re: pgsql: Fix handling of HBA ldapserver with multiple hostnames.