Fix a couple of lingering references to POSTQUEL query syntax, per Simon.

src/backend/executor/execProcnode.c

@@ -12,7 +12,7 @@
  *
  *
  * IDENTIFICATION
- *	  $PostgreSQL: pgsql/src/backend/executor/execProcnode.c,v 1.51 2005/10/15 02:49:16 momjian Exp $
+ *	  $PostgreSQL: pgsql/src/backend/executor/execProcnode.c,v 1.52 2005/12/07 15:27:42 tgl Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -29,10 +29,10 @@
  *		and ExecEndNode in sync when new nodes are added.
  *
  *	 EXAMPLE
- *		suppose we want the age of the manager of the shoe department and
- *		the number of employees in that department.  so we have the query:
+ *		Suppose we want the age of the manager of the shoe department and
+ *		the number of employees in that department.  So we have the query:
  *
- *				retrieve (DEPT.no_emps, EMP.age)
+ *				select DEPT.no_emps, EMP.age
  *				where EMP.name = DEPT.mgr and
  *					  DEPT.name = "shoe"
  *

src/backend/executor/execTuples.c

@@ -15,7 +15,7 @@
  *
  *
  * IDENTIFICATION
- *	  $PostgreSQL: pgsql/src/backend/executor/execTuples.c,v 1.90 2005/11/25 04:24:48 tgl Exp $
+ *	  $PostgreSQL: pgsql/src/backend/executor/execTuples.c,v 1.91 2005/12/07 15:27:42 tgl Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -48,7 +48,7 @@
  *		ExecTypeFromTL			- form a TupleDesc from a target list
  *
  *	 EXAMPLE OF HOW TABLE ROUTINES WORK
- *		Suppose we have a query such as retrieve (EMP.name) and we have
+ *		Suppose we have a query such as SELECT emp.name FROM emp and we have
  *		a single SeqScan node in the query plan.
  *
  *		At ExecutorStart()