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 5b8eb21e3c74b3821ec7157c55fd837861f69114..be08cb1748bcba54f119eddc4636e225ef1edccc 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