|
12 | 12 | * This information is needed by routines manipulating tuples |
13 | 13 | * (getattribute, formtuple, etc.). |
14 | 14 | * |
15 | | - * Portions Copyright (c) 1996-2018, PostgreSQL Global Development Group |
16 | | - * Portions Copyright (c) 1994, Regents of the University of California |
17 | | - * |
18 | | - * |
19 | | - * IDENTIFICATION |
20 | | - * src/backend/executor/execTuples.c |
21 | | - * |
22 | | - *------------------------------------------------------------------------- |
23 | | - */ |
24 | | -/* |
25 | | - * INTERFACE ROUTINES |
26 | | - * |
27 | | - * SLOT CREATION/DESTRUCTION |
28 | | - *MakeTupleTableSlot- create an empty slot |
29 | | - *ExecAllocTableSlot- create a slot within a tuple table |
30 | | - *ExecResetTupleTable- clear and optionally delete a tuple table |
31 | | - *MakeSingleTupleTableSlot - make a standalone slot, set its descriptor |
32 | | - *ExecDropSingleTupleTableSlot - destroy a standalone slot |
33 | | - * |
34 | | - * SLOT ACCESSORS |
35 | | - *ExecSetSlotDescriptor- set a slot's tuple descriptor |
36 | | - *ExecStoreTuple- store a physical tuple in the slot |
37 | | - *ExecStoreMinimalTuple- store a minimal physical tuple in the slot |
38 | | - *ExecClearTuple- clear contents of a slot |
39 | | - *ExecStoreVirtualTuple- mark slot as containing a virtual tuple |
40 | | - *ExecCopySlotTuple- build a physical tuple from a slot |
41 | | - *ExecCopySlotMinimalTuple - build a minimal physical tuple from a slot |
42 | | - *ExecMaterializeSlot- convert virtual to physical storage |
43 | | - *ExecCopySlot- copy one slot's contents to another |
44 | | - * |
45 | | - * CONVENIENCE INITIALIZATION ROUTINES |
46 | | - *ExecInitResultTupleSlot \convenience routines to initialize |
47 | | - *ExecInitScanTupleSlot\the various tuple slots for nodes |
48 | | - *ExecInitExtraTupleSlot/which store copies of tuples. |
49 | | - *ExecInitNullTupleSlot / |
50 | | - * |
51 | | - * Routines that probably belong somewhere else: |
52 | | - *ExecTypeFromTL- form a TupleDesc from a target list |
53 | 15 | * |
54 | 16 | * EXAMPLE OF HOW TABLE ROUTINES WORK |
55 | 17 | *Suppose we have a query such as SELECT emp.name FROM emp and we have |
|
78 | 40 | *(such as whether or not a tuple should be pfreed, what buffer contains |
79 | 41 | *this tuple, the tuple's tuple descriptor, etc). It also allows us |
80 | 42 | *to avoid physically constructing projection tuples in many cases. |
| 43 | + * |
| 44 | + * |
| 45 | + * Portions Copyright (c) 1996-2018, PostgreSQL Global Development Group |
| 46 | + * Portions Copyright (c) 1994, Regents of the University of California |
| 47 | + * |
| 48 | + * |
| 49 | + * IDENTIFICATION |
| 50 | + * src/backend/executor/execTuples.c |
| 51 | + * |
| 52 | + *------------------------------------------------------------------------- |
81 | 53 | */ |
82 | 54 | #include"postgres.h" |
83 | 55 |
|
|