pgsql: Adjust DSM and DSA slot usage constants. - Mailing list pgsql-committers

From Thomas Munro
Subject pgsql: Adjust DSM and DSA slot usage constants.
Date
Msg-id E1ixNyb-0003to-Tg@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Adjust DSM and DSA slot usage constants.

When running a lot of large parallel queries concurrently, or a plan with
a lot of separate Gather nodes, it is possible to run out of DSM slots.
There are better solutions to these problems requiring architectural
redesign work, but for now, let's adjust the constants so that it's more
difficult to hit the limit.

1.  Previously, a DSA area would create up to four segments at each size
before doubling the size.  After this commit, it will create only two at
each size, so it ramps up faster and therefore needs fewer slots.

2.  Previously, the total limit on DSM slots allowed for 2 per connection.
Switch to 5 per connection.

Also remove an obsolete nearby comment.

Author: Thomas Munro
Reviewed-by: Robert Haas, Andres Freund
Discussion: https://postre.es/m/CA%2BhUKGL6H2BpGbiF7Lj6QiTjTGyTLW_vLR%3DSn2tEBeTcYXiMKw%40mail.gmail.com

Branch
------
master

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

Modified Files
--------------
src/backend/storage/ipc/dsm.c | 7 +------
src/backend/utils/mmgr/dsa.c  | 2 +-
2 files changed, 2 insertions(+), 7 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: In jsonb_plpython.c, suppress warning message from gcc 10.
Next
From: Michael Paquier
Date:
Subject: pgsql: Fix typo in recently-added TAP test for replication slots