pgsql: Don't leak a signalfd when using latches in the postmaster. - Mailing list pgsql-committers

From Thomas Munro
Subject pgsql: Don't leak a signalfd when using latches in the postmaster.
Date
Msg-id E1p8cg7-0050Jf-I9@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Don't leak a signalfd when using latches in the postmaster.

At the time of commit 6a2a70a02 we didn't use latch infrastructure in
the postmaster.  We're planning to start doing that, so we'd better make
sure that the signalfd inherited from a postmaster is not duplicated and
then leaked in the child.

Reviewed-by: Andres Freund <andres@anarazel.de>
Reviewed-by: Justin Pryzby <pryzby@telsasoft.com>
Discussion: https://postgr.es/m/CA%2BhUKG%2BZ-HpOj1JsO9eWUP%2Bar7npSVinsC_npxSy%2BjdOMsx%3DGg%40mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1f0019de2fe374fa54fca277f36c2e754894db30

Modified Files
--------------
src/backend/storage/ipc/latch.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Update upgrade_adapt.sql to handle tables using aclitem as data
Next
From: David Rowley
Date:
Subject: pgsql: Fix bug in translate_col_privs_multilevel