Put back example of using Result node to execute an INSERT.

diff --git a/src/backend/executor/nodeResult.c b/src/backend/executor/nodeResult.c
index ee6c91cb9dc0a79153d1008a6fd3bc9e36e22564..7c77dc0712113b87989364e6d0232a7c24a00568 100644 (file)
--- a/src/backend/executor/nodeResult.c
+++ b/src/backend/executor/nodeResult.c
@@ -10,6 +10,11 @@
  *
  *             select 1 * 2
  *
+ *             insert into emp values ('mike', 15000)
+ *
+ *     (Remember that in an INSERT or UPDATE, we need a plan tree that
+ *     generates the new rows.)
+ *
  *     Result nodes are also used to optimise queries with constant
  *     qualifications (ie, quals that do not depend on the scanned data),
  *     such as:
@@ -20,7 +25,7 @@
  *
  *                     Result  (with 2 > 1 qual)
  *                     /
- *                SeqScan (emp.all)
+ *                SeqScan (emp.*)
  *
  *     At runtime, the Result node evaluates the constant qual once,
  *     which is shown by EXPLAIN as a One-Time Filter.  If it's
@@ -33,7 +38,7 @@
  * Portions Copyright (c) 1994, Regents of the University of California
  *
  * IDENTIFICATION
- *   $PostgreSQL: pgsql/src/backend/executor/nodeResult.c,v 1.30 2005/04/24 11:46:21 neilc Exp $
+ *   $PostgreSQL: pgsql/src/backend/executor/nodeResult.c,v 1.31 2005/04/24 15:32:07 tgl Exp $
  *
  *-------------------------------------------------------------------------
  */