OSDN Git Service

Update some comments to use SQL examples rather than QUEL. From Simon
authorNeil Conway <neilc@samurai.com>
Sun, 24 Apr 2005 11:46:21 +0000 (11:46 +0000)
committerNeil Conway <neilc@samurai.com>
Sun, 24 Apr 2005 11:46:21 +0000 (11:46 +0000)
Riggs.

src/backend/executor/nodeAppend.c
src/backend/executor/nodeResult.c

index 9660f1e..0f77741 100644 (file)
@@ -8,7 +8,7 @@
  *
  *
  * IDENTIFICATION
- *       $PostgreSQL: pgsql/src/backend/executor/nodeAppend.c,v 1.62 2004/12/31 21:59:45 pgsql Exp $
+ *       $PostgreSQL: pgsql/src/backend/executor/nodeAppend.c,v 1.63 2005/04/24 11:46:20 neilc Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -43,7 +43,7 @@
  *             and student-emp inherits from student and employee, the
  *             query:
  *
- *                             retrieve (e.name) from e in person*
+ *                             select name from person
  *
  *             generates the plan:
  *
index abc94a2..ee6c91c 100644 (file)
@@ -8,15 +8,13 @@
  *             Result nodes are used in queries where no relations are scanned.
  *             Examples of such queries are:
  *
- *                             retrieve (x = 1)
- *             and
- *                             append emp (name = "mike", salary = 15000)
+ *                             select 1 * 2
  *
  *             Result nodes are also used to optimise queries with constant
  *             qualifications (ie, quals that do not depend on the scanned data),
  *             such as:
  *
- *                             retrieve (emp.all) where 2 > 1
+ *                             select * from emp where 2 > 1
  *
  *             In this case, the plan generated is
  *
  *                                             /
  *                                SeqScan (emp.all)
  *
- *             At runtime, the Result node evaluates the constant qual once.
- *             If it's false, we can return an empty result set without running
- *             the controlled plan at all.  If it's true, we run the controlled
+ *             At runtime, the Result node evaluates the constant qual once,
+ *             which is shown by EXPLAIN as a One-Time Filter.  If it's
+ *             false, we can return an empty result set without running the
+ *             controlled plan at all.  If it's true, we run the controlled
  *             plan normally and pass back the results.
  *
  *
@@ -34,7 +33,7 @@
  * Portions Copyright (c) 1994, Regents of the University of California
  *
  * IDENTIFICATION
- *       $PostgreSQL: pgsql/src/backend/executor/nodeResult.c,v 1.29 2004/12/31 21:59:45 pgsql Exp $
+ *       $PostgreSQL: pgsql/src/backend/executor/nodeResult.c,v 1.30 2005/04/24 11:46:21 neilc Exp $
  *
  *-------------------------------------------------------------------------
  */