|
8 | 8 | * |
9 | 9 | * |
10 | 10 | * IDENTIFICATION |
11 | | - * $PostgreSQL: pgsql/src/backend/executor/nodeUnique.c,v 1.41 2003/11/29 19:51:48 pgsql Exp $ |
| 11 | + * $PostgreSQL: pgsql/src/backend/executor/nodeUnique.c,v 1.42 2004/03/02 22:05:24 tgl Exp $ |
12 | 12 | * |
13 | 13 | *------------------------------------------------------------------------- |
14 | 14 | */ |
@@ -104,9 +104,13 @@ ExecUnique(UniqueState *node) |
104 | 104 | * |
105 | 105 | * Note that we manage the copy ourselves.We can't rely on the result |
106 | 106 | * tuple slot to maintain the tuple reference because our caller may |
107 | | - * replace the slot contents with a different tuple (see junk filter |
108 | | - * handling in execMain.c). We assume that the caller will no longer |
109 | | - * be interested in the current tuple after he next calls us. |
| 107 | + * replace the slot contents with a different tuple. We assume that |
| 108 | + * the caller will no longer be interested in the current tuple after |
| 109 | + * he next calls us. |
| 110 | + * |
| 111 | + * tgl 3/2004: the above concern is no longer valid; junkfilters used to |
| 112 | + * modify their input's return slot but don't anymore, and I don't think |
| 113 | + * anyplace else does either. Not worth changing this code though. |
110 | 114 | */ |
111 | 115 | if (node->priorTuple!=NULL) |
112 | 116 | heap_freetuple(node->priorTuple); |
|