|
68 | 68 | * A TupleTableSlot can also be "empty", indicated by flag TTS_FLAG_EMPTY set
|
69 | 69 | * in tts_flags, holding no valid data. This is the only valid state for a
|
70 | 70 | * freshly-created slot that has not yet had a tuple descriptor assigned to
|
71 |
| - * it. In this state, TTS_SHOULDFREE should not be set in tts_flags, tts_tuple |
72 |
| - * must be NULL and tts_nvalid zero. |
| 71 | + * it. In this state, TTS_FLAG_SHOULDFREE should not be set in tts_flags and |
| 72 | + * tts_nvalid should be set to zero. |
73 | 73 | *
|
74 | 74 | * The tupleDescriptor is simply referenced, not copied, by the TupleTableSlot
|
75 | 75 | * code. The caller of ExecSetSlotDescriptor() is responsible for providing
|
|
79 | 79 | * mechanism to do more. However, the slot will increment the tupdesc
|
80 | 80 | * reference count if a reference-counted tupdesc is supplied.)
|
81 | 81 | *
|
82 |
| - * When TTS_SHOULDFREE is set in tts_flags, the physical tuple is "owned" by |
83 |
| - * the slot and should be freed when the slot's reference to the tuple is |
| 82 | + * When TTS_FLAG_SHOULDFREE is set in tts_flags, the physical tuple is "owned" |
| 83 | + * by the slot and should be freed when the slot's reference to the tuple is |
84 | 84 | * dropped.
|
85 | 85 | *
|
86 | 86 | * tts_values/tts_isnull are allocated either when the slot is created (when
|
@@ -268,7 +268,7 @@ typedef struct BufferHeapTupleTableSlot
|
268 | 268 | * If buffer is not InvalidBuffer, then the slot is holding a pin on the
|
269 | 269 | * indicated buffer page; drop the pin when we release the slot's
|
270 | 270 | * reference to that buffer. (TTS_FLAG_SHOULDFREE should not be set in
|
271 |
| - * such a case, since presumably tts_tuple is pointing into the buffer.) |
| 271 | + * such a case, since presumably base.tuple is pointing into the buffer.) |
272 | 272 | */
|
273 | 273 | Buffer buffer; /* tuple's buffer, or InvalidBuffer */
|
274 | 274 | } BufferHeapTupleTableSlot;
|
|
0 commit comments