Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitf519d04

Browse files
committed
Update comment that I missed the first time around.
1 parent191b13a commitf519d04

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎src/backend/storage/ipc/procarray.c

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@
1818
*
1919
*
2020
* IDENTIFICATION
21-
* $PostgreSQL: pgsql/src/backend/storage/ipc/procarray.c,v 1.1 2005/05/1921:35:46 tgl Exp $
21+
* $PostgreSQL: pgsql/src/backend/storage/ipc/procarray.c,v 1.2 2005/05/1923:57:11 tgl Exp $
2222
*
2323
*-------------------------------------------------------------------------
2424
*/
@@ -442,8 +442,8 @@ GetSnapshotData(Snapshot snapshot, bool serializable)
442442

443443
/*
444444
* Allocating space for MaxBackends xids is usually overkill;
445-
*lastBackend would be sufficient. But it seems better to do the
446-
* malloc while not holding the lock, so we can't look atlastBackend.
445+
*numProcs would be sufficient. But it seems better to do the
446+
* malloc while not holding the lock, so we can't look atnumProcs.
447447
*
448448
* This does open a possibility for avoiding repeated malloc/free: since
449449
* MaxBackends does not change at runtime, we can simply reuse the

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp