aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2005-05-19 23:57:11 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2005-05-19 23:57:11 +0000
commitf519d04a436b98cee20aecd59646f18c2915616b (patch)
tree0e9d355e149b20e4fa19b57f094b4ba67ba73053
parent191b13aacaae7557d3eab6733c06269ce2c0993a (diff)
downloadpostgresql-f519d04a436b98cee20aecd59646f18c2915616b.tar.gz
postgresql-f519d04a436b98cee20aecd59646f18c2915616b.zip
Update comment that I missed the first time around.
-rw-r--r--src/backend/storage/ipc/procarray.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/storage/ipc/procarray.c b/src/backend/storage/ipc/procarray.c
index 85ae3c762ba..23b198b1497 100644
--- a/src/backend/storage/ipc/procarray.c
+++ b/src/backend/storage/ipc/procarray.c
@@ -18,7 +18,7 @@
*
*
* 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;
- * lastBackend would be sufficient. But it seems better to do the
- * malloc while not holding the lock, so we can't look at lastBackend.
+ * numProcs would be sufficient. But it seems better to do the
+ * malloc while not holding the lock, so we can't look at numProcs.
*
* This does open a possibility for avoiding repeated malloc/free: since
* MaxBackends does not change at runtime, we can simply reuse the