From: Tom Lane Date: Thu, 19 May 2005 23:57:11 +0000 (+0000) Subject: Update comment that I missed the first time around. X-Git-Tag: REL8_1_0BETA1~770 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f519d04a436b98cee20aecd59646f18c2915616b;p=postgresql Update comment that I missed the first time around. --- diff --git a/src/backend/storage/ipc/procarray.c b/src/backend/storage/ipc/procarray.c index 85ae3c762b..23b198b149 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