pgsql: Don't leak a signalfd when using latches in the postmaster.

From: Thomas Munro <tmunro(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Don't leak a signalfd when using latches in the postmaster.
Date: 2022-12-23 07:41:16
Message-ID: E1p8cg7-0050Jf-I9@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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(at)anarazel(dot)de>
Reviewed-by: Justin Pryzby <pryzby(at)telsasoft(dot)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(+)

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2022-12-23 11:59:03 pgsql: Fix bug in translate_col_privs_multilevel
Previous Message Michael Paquier 2022-12-23 02:37:21 pgsql: Update upgrade_adapt.sql to handle tables using aclitem as data