mirror of
https://github.com/postgres/postgres.git
synced 2025-05-08 07:21:33 +03:00
Update comment that I missed the first time around.
This commit is contained in:
parent
191b13aaca
commit
f519d04a43
@ -18,7 +18,7 @@
|
|||||||
*
|
*
|
||||||
*
|
*
|
||||||
* IDENTIFICATION
|
* IDENTIFICATION
|
||||||
* $PostgreSQL: pgsql/src/backend/storage/ipc/procarray.c,v 1.1 2005/05/19 21:35:46 tgl Exp $
|
* $PostgreSQL: pgsql/src/backend/storage/ipc/procarray.c,v 1.2 2005/05/19 23:57:11 tgl Exp $
|
||||||
*
|
*
|
||||||
*-------------------------------------------------------------------------
|
*-------------------------------------------------------------------------
|
||||||
*/
|
*/
|
||||||
@ -442,8 +442,8 @@ GetSnapshotData(Snapshot snapshot, bool serializable)
|
|||||||
|
|
||||||
/*
|
/*
|
||||||
* Allocating space for MaxBackends xids is usually overkill;
|
* Allocating space for MaxBackends xids is usually overkill;
|
||||||
* lastBackend would be sufficient. But it seems better to do the
|
* numProcs would be sufficient. But it seems better to do the
|
||||||
* malloc while not holding the lock, so we can't look at lastBackend.
|
* malloc while not holding the lock, so we can't look at numProcs.
|
||||||
*
|
*
|
||||||
* This does open a possibility for avoiding repeated malloc/free: since
|
* This does open a possibility for avoiding repeated malloc/free: since
|
||||||
* MaxBackends does not change at runtime, we can simply reuse the
|
* MaxBackends does not change at runtime, we can simply reuse the
|
||||||
|
Loading…
x
Reference in New Issue
Block a user