|
15 | 15 | * |
16 | 16 | * |
17 | 17 | * IDENTIFICATION |
18 | | - * $PostgreSQL: pgsql/src/backend/executor/execTuples.c,v 1.85 2005/03/16 21:38:07 tgl Exp $ |
| 18 | + * $PostgreSQL: pgsql/src/backend/executor/execTuples.c,v 1.86 2005/03/17 15:25:51 tgl Exp $ |
19 | 19 | * |
20 | 20 | *------------------------------------------------------------------------- |
21 | 21 | */ |
|
51 | 51 | *Suppose we have a query such as retrieve (EMP.name) and we have |
52 | 52 | *a single SeqScan node in the query plan. |
53 | 53 | * |
54 | | - *AtExecStart() |
| 54 | + *AtExecutorStart() |
55 | 55 | *---------------- |
56 | 56 | *- InitPlan() calls ExecCreateTupleTable() to create the tuple |
57 | 57 | * table which will hold tuples processed by the executor. |
|
61 | 61 | * table for the tuples returned by the access methods and the |
62 | 62 | * tuples resulting from performing target list projections. |
63 | 63 | * |
64 | | - *DuringExecRun() |
| 64 | + *DuringExecutorRun() |
65 | 65 | *---------------- |
66 | 66 | *- SeqNext() calls ExecStoreTuple() to place the tuple returned |
67 | 67 | * by the access methods into the scan tuple slot. |
68 | 68 | * |
69 | 69 | *- ExecSeqScan() calls ExecStoreTuple() to take the result |
70 | 70 | * tuple from ExecProject() and place it into the result tuple slot. |
71 | 71 | * |
72 | | - *- ExecutePlan() callsExecRetrieve() whichgets thetuple out of |
73 | | - *the slot passedtoit (by direct accesstoslot->val, which is |
74 | | - *ugly but not worth changing). this tuple is then returned. |
| 72 | + *- ExecutePlan() callsExecSelect(), whichpasses theresult slot |
| 73 | + * toprinttup(), which uses slot_getallattrs()toextract the |
| 74 | + *individual Datums for printing. |
75 | 75 | * |
76 | | - *AtExecEnd() |
| 76 | + *AtExecutorEnd() |
77 | 77 | *---------------- |
78 | 78 | *- EndPlan() calls ExecDropTupleTable() to clean up any remaining |
79 | 79 | * tuples left over from executing the query. |
|