From: Robert Haas <rhaas@postgresql.org>
Date: Mon, 26 Sep 2011 17:12:22 +0000 (-0400)
Subject: Update obsolete comments.
X-Git-Tag: REL9_2_BETA1~1059
X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=821fd903f9b7f5a8ca439b9b7cb6d2f54672582f;p=postgresql.git

Update obsolete comments.

This was partially fixed by 57fdb2b0d835fe201434fc28bf5dabf83ada26d1,
back in 2005, but it missed a couple of spots.

YAMAMOTO Takashi
---

diff --git a/src/backend/executor/execProcnode.c b/src/backend/executor/execProcnode.c
index 8bdfad22223..284fc6a63b7 100644
--- a/src/backend/executor/execProcnode.c
+++ b/src/backend/executor/execProcnode.c
@@ -55,7 +55,7 @@
  *		of ExecInitNode() is a plan state tree built with the same structure
  *		as the underlying plan tree.
  *
- *	  * Then when ExecRun() is called, it calls ExecutePlan() which calls
+ *	  * Then when ExecutorRun() is called, it calls ExecutePlan() which calls
  *		ExecProcNode() repeatedly on the top node of the plan state tree.
  *		Each time this happens, ExecProcNode() will end up calling
  *		ExecNestLoop(), which calls ExecProcNode() on its subplans.
@@ -65,7 +65,7 @@
  *		form the tuples it returns.
  *
  *	  * Eventually ExecSeqScan() stops returning tuples and the nest
- *		loop join ends.  Lastly, ExecEnd() calls ExecEndNode() which
+ *		loop join ends.  Lastly, ExecutorEnd() calls ExecEndNode() which
  *		calls ExecEndNestLoop() which in turn calls ExecEndNode() on
  *		its subplans which result in ExecEndSeqScan().
  *