Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 24475a7

Browse files
committed
Put back example of using Result node to execute an INSERT.
1 parent cdf39c7 commit 24475a7

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

src/backend/executor/nodeResult.c

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,11 @@
1010
*
1111
* select 1 * 2
1212
*
13+
* insert into emp values ('mike', 15000)
14+
*
15+
* (Remember that in an INSERT or UPDATE, we need a plan tree that
16+
* generates the new rows.)
17+
*
1318
* Result nodes are also used to optimise queries with constant
1419
* qualifications (ie, quals that do not depend on the scanned data),
1520
* such as:
@@ -20,7 +25,7 @@
2025
*
2126
* Result (with 2 > 1 qual)
2227
* /
23-
* SeqScan (emp.all)
28+
* SeqScan (emp.*)
2429
*
2530
* At runtime, the Result node evaluates the constant qual once,
2631
* which is shown by EXPLAIN as a One-Time Filter. If it's
@@ -33,7 +38,7 @@
3338
* Portions Copyright (c) 1994, Regents of the University of California
3439
*
3540
* IDENTIFICATION
36-
* $PostgreSQL: pgsql/src/backend/executor/nodeResult.c,v 1.30 2005/04/24 11:46:21 neilc Exp $
41+
* $PostgreSQL: pgsql/src/backend/executor/nodeResult.c,v 1.31 2005/04/24 15:32:07 tgl Exp $
3742
*
3843
*-------------------------------------------------------------------------
3944
*/

0 commit comments

Comments
 (0)