rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

As long as we're fixing this space calculation, let's actually do it 

right.  We should MAXALIGN the individual items because we'll
allocate them individually, not as an array.
This commit is contained in:
Tom Lane 2001-02-23 20:12:37 +00:00
parent d106fd2fa8
commit e74ce0a566
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/backend/storage/lmgr/lock.c
View File

@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/storage/lmgr/lock.c,v 1.84 2001/02/23 18:28:46 momjian Exp $
* $Header: /cvsroot/pgsql/src/backend/storage/lmgr/lock.c,v 1.85 2001/02/23 20:12:37 tgl Exp $
*
* NOTES
* Outside modules can create a lock table and acquire/release
@ -1410,8 +1410,8 @@ LockShmemSize(int maxBackends)
int size = 0;
size += MAXALIGN(sizeof(PROC_HDR)); /* ProcGlobal */
size += MAXALIGN(maxBackends * sizeof(PROC)); /* each MyProc */
size += MAXALIGN(MAX_LOCK_METHODS * sizeof(LOCKMETHODCTL)); /* each lockMethodTable->ctl */
size += maxBackends * MAXALIGN(sizeof(PROC)); /* each MyProc */
size += MAX_LOCK_METHODS * MAXALIGN(sizeof(LOCKMETHODCTL)); /* each lockMethodTable->ctl */
/* lockHash table */
size += hash_estimate_size(NLOCKENTS(maxBackends),