diff options
| author | Robert Haas <rhaas@postgresql.org> | 2022-04-12 14:45:23 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2022-04-12 14:45:23 -0400 |
| commit | 7fc0e7de9fb8306e84d1c15211aba4308f694455 (patch) | |
| tree | ce8d0213123959bce52699e8e8d837d46758a2f6 /src/backend/storage/ipc/dsm.c | |
| parent | 2c9381840fe2d6d1c3179350493fe5fd3dcf90b5 (diff) | |
Revert the addition of GetMaxBackends() and related stuff.
This reverts commits 0147fc7, 4567596, aa64f23, and 5ecd018.
There is no longer agreement that introducing this function
was the right way to address the problem. The consensus now
seems to favor trying to make a correct value for MaxBackends
available to mdules executing their _PG_init() functions.
Nathan Bossart
Discussion: http://postgr.es/m/20220323045229.i23skfscdbvrsuxa@jrouhaud
Diffstat (limited to 'src/backend/storage/ipc/dsm.c')
| -rw-r--r-- | src/backend/storage/ipc/dsm.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/storage/ipc/dsm.c b/src/backend/storage/ipc/dsm.c index ce6f07d4c58..9d86bbe8724 100644 --- a/src/backend/storage/ipc/dsm.c +++ b/src/backend/storage/ipc/dsm.c @@ -166,7 +166,7 @@ dsm_postmaster_startup(PGShmemHeader *shim) /* Determine size for new control segment. */ maxitems = PG_DYNSHMEM_FIXED_SLOTS - + PG_DYNSHMEM_SLOTS_PER_BACKEND * GetMaxBackends(); + + PG_DYNSHMEM_SLOTS_PER_BACKEND * MaxBackends; elog(DEBUG2, "dynamic shared memory system will support %u segments", maxitems); segsize = dsm_control_bytes_needed(maxitems); |