| From: | Amit Kapila <akapila(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Fix the initialization of atomic variable introduced by the |
| Date: | 2018-11-13 05:40:55 |
| Message-ID: | E1gMRRX-0000Jw-Gh@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix the initialization of atomic variable introduced by the
group clearing mechanism.
Commit 0e141c0fbb introduced initialization of atomic variable in
InitProcess which means that it's not safe to look at it for backends that
aren't currently in use. Fix that by initializing the same 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
------
REL9_6_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/1a8bde490c982cbdd9d174e72d42f6042e9bf4ee
Modified Files
--------------
src/backend/storage/lmgr/proc.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
| 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. |