pgsql: Fix overflow with pgstats DSA reference count - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: Fix overflow with pgstats DSA reference count
Date
Msg-id E1sMdGI-003AZ9-87@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix overflow with pgstats DSA reference count

When pgstats is initialized for a backend, it uses dsa_attach_in_place()
without a "segment" provided.  Hence, no callback is registered to
automatically release the DSA attached once a backend exits.  Not doing
any cleanup causes the reference count of the pgstats DSA to
continuously increment, at some point overflowing it (the more the
number of connections, the faster it is to reach this state).  Once the
reference count overflows and then gets back to 0, new backends are not
able to attach to the pgstats DSA, failing startup.

This issue is resolved by adding in the pgstats shutdown hook a call to
dsa_release_in_place(), ensuring that the DSA attached at backend
startup is correctly released, keeping the reference count at bay.

The author of this patch has been able to see this issue on a server
with a long uptime and a high connection turnover.

Issue introduced by 5891c7a8ed8f, so backpatch down to 15.

Author: Anthonin Bonnefoy
Discussion: https://postgr.es/m/CAO6_XqqJbJBL=M7Ym13TcB4Xnq58vRa2jcC+gwEPBgbAda6B1Q@mail.gmail.com
Backpatch-through: 15

Branch
------
REL_15_STABLE

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

Modified Files
--------------
src/backend/utils/activity/pgstat_shmem.c | 8 ++++++++
1 file changed, 8 insertions(+)


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: Fix bugs in MultiXact truncation
Next
From: Amit Kapila
Date:
Subject: pgsql: Drop the temporary tuple slots allocated by pgoutput.