Update obsolete comment.

tglsfdc · tglsfdc · commit 57fdb2b0d835 · 2005-03-17T15:25:51.000Z
diff --git a/src/backend/executor/execTuples.c b/src/backend/executor/execTuples.c
@@ -15,7 +15,7 @@
  *
  *
  * IDENTIFICATION
- *	  $PostgreSQL: pgsql/src/backend/executor/execTuples.c,v 1.85 2005/03/16 21:38:07 tgl Exp $
+ *	  $PostgreSQL: pgsql/src/backend/executor/execTuples.c,v 1.86 2005/03/17 15:25:51 tgl Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -51,7 +51,7 @@
  *		Suppose we have a query such as retrieve (EMP.name) and we have
  *		a single SeqScan node in the query plan.
  *
- *		At ExecStart()
+ *		At ExecutorStart()
  *		----------------
  *		- InitPlan() calls ExecCreateTupleTable() to create the tuple
  *		  table which will hold tuples processed by the executor.
@@ -61,19 +61,19 @@
  *		  table for the tuples returned by the access methods and the
  *		  tuples resulting from performing target list projections.
  *
- *		During ExecRun()
+ *		During ExecutorRun()
  *		----------------
  *		- SeqNext() calls ExecStoreTuple() to place the tuple returned
  *		  by the access methods into the scan tuple slot.
  *
  *		- ExecSeqScan() calls ExecStoreTuple() to take the result
  *		  tuple from ExecProject() and place it into the result tuple slot.
  *
- *		- ExecutePlan() calls ExecRetrieve() which gets the tuple out of
- *		  the slot passed to it (by direct access to slot->val, which is
- *		  ugly but not worth changing).  this tuple is then returned.
+ *		- ExecutePlan() calls ExecSelect(), which passes the result slot
+ *		  to printtup(), which uses slot_getallattrs() to extract the
+ *		  individual Datums for printing.
  *
- *		At ExecEnd()
+ *		At ExecutorEnd()
  *		----------------
  *		- EndPlan() calls ExecDropTupleTable() to clean up any remaining
  *		  tuples left over from executing the query.

Original file line number	Diff line number	Diff line change
`@@ -15,7 +15,7 @@`
`15`	`15`	`*`
`16`	`16`	`*`
`17`	`17`	`* IDENTIFICATION`
`18`		`- * $PostgreSQL: pgsql/src/backend/executor/execTuples.c,v 1.85 2005/03/16 21:38:07 tgl Exp $`
	`18`	`+ * $PostgreSQL: pgsql/src/backend/executor/execTuples.c,v 1.86 2005/03/17 15:25:51 tgl Exp $`
`19`	`19`	`*`
`20`	`20`	`*-------------------------------------------------------------------------`
`21`	`21`	`*/`
`@@ -51,7 +51,7 @@`
`51`	`51`	`* Suppose we have a query such as retrieve (EMP.name) and we have`
`52`	`52`	`* a single SeqScan node in the query plan.`
`53`	`53`	`*`
`54`		`- * At ExecStart()`
	`54`	`+ * At ExecutorStart()`
`55`	`55`	`* ----------------`
`56`	`56`	`* - InitPlan() calls ExecCreateTupleTable() to create the tuple`
`57`	`57`	`* table which will hold tuples processed by the executor.`
`@@ -61,19 +61,19 @@`
`61`	`61`	`* table for the tuples returned by the access methods and the`
`62`	`62`	`* tuples resulting from performing target list projections.`
`63`	`63`	`*`
`64`		`- * During ExecRun()`
	`64`	`+ * During ExecutorRun()`
`65`	`65`	`* ----------------`
`66`	`66`	`* - SeqNext() calls ExecStoreTuple() to place the tuple returned`
`67`	`67`	`* by the access methods into the scan tuple slot.`
`68`	`68`	`*`
`69`	`69`	`* - ExecSeqScan() calls ExecStoreTuple() to take the result`
`70`	`70`	`* tuple from ExecProject() and place it into the result tuple slot.`
`71`	`71`	`*`
`72`		`- * - ExecutePlan() calls ExecRetrieve() which gets the tuple out of`
`73`		`- * the slot passed to it (by direct access to slot->val, which is`
`74`		`- * ugly but not worth changing). this tuple is then returned.`
	`72`	`+ * - ExecutePlan() calls ExecSelect(), which passes the result slot`
	`73`	`+ * to printtup(), which uses slot_getallattrs() to extract the`
	`74`	`+ * individual Datums for printing.`
`75`	`75`	`*`
`76`		`- * At ExecEnd()`
	`76`	`+ * At ExecutorEnd()`
`77`	`77`	`* ----------------`
`78`	`78`	`* - EndPlan() calls ExecDropTupleTable() to clean up any remaining`
`79`	`79`	`* tuples left over from executing the query.`