|
7 | 7 | * Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group |
8 | 8 | * Portions Copyright (c) 1994, Regents of the University of California |
9 | 9 | * |
10 | | - * $Id: execdebug.h,v 1.15 2001/01/24 19:43:23 momjian Exp $ |
| 10 | + * $Id: execdebug.h,v 1.16 2001/09/20 21:07:57 tgl Exp $ |
11 | 11 | * |
12 | 12 | *------------------------------------------------------------------------- |
13 | 13 | */ |
|
27 | 27 | * ---------------------------------------------------------------- |
28 | 28 | */ |
29 | 29 |
|
30 | | -/* ---------------- |
31 | | - *EXEC_DEBUGSTORETUP is for tuple table debugging - this |
32 | | - *will print a message every time we call ExecStoreTuple. |
33 | | - *-cim 3/20/91 |
34 | | - * ---------------- |
35 | | -#undef EXEC_DEBUGSTORETUP |
36 | | - */ |
37 | | - |
38 | 30 | /* ---------------- |
39 | 31 | *EXEC_TUPLECOUNT is a #define which causes the |
40 | 32 | *executor keep track of tuple counts. This might be |
|
45 | 37 | #undef EXEC_TUPLECOUNT |
46 | 38 | */ |
47 | 39 |
|
48 | | -/* ---------------- |
49 | | - *EXEC_SHOWBUFSTATS controls whether or not buffer statistics |
50 | | - *are shown for each query. -cim 2/9/89 |
51 | | - * ---------------- |
52 | | -#undef EXEC_SHOWBUFSTATS |
53 | | - */ |
54 | | - |
55 | 40 | /* ---------------- |
56 | 41 | *EXEC_CONTEXTDEBUG turns on the printing of debugging information |
57 | 42 | *by CXT_printf() calls regarding which memory context is the |
|
60 | 45 | #undef EXEC_CONTEXTDEBUG |
61 | 46 | */ |
62 | 47 |
|
63 | | -/* ---------------- |
64 | | - *EXEC_RETURNSIZE is a compile flag governing the |
65 | | - *behaviour of lispFmgr.. See ExecMakeFunctionResult(). |
66 | | - *Undefining this avoids a problem in the system cache. |
67 | | - * |
68 | | - *Note: undefining this means that there is incorrect |
69 | | - * information in the const nodes corresponding |
70 | | - * to function (or operator) results. The thing is, |
71 | | - * 99% of the time this is fine because when you do |
72 | | - * something like x = emp.sal + 1, you already know |
73 | | - * the type and size of x so the fact that + didn't |
74 | | - * return the correct size doesn't matter. |
75 | | - * With variable length stuff the size is stored in |
76 | | - * the first few bytes of the data so again, it's |
77 | | - * not likely to matter. |
78 | | - * ---------------- |
79 | | -#undef EXEC_RETURNSIZE |
80 | | - */ |
81 | | - |
82 | 48 | /* ---------------- |
83 | 49 | *EXEC_UTILSDEBUG is a flag which turns on debugging of the |
84 | 50 | *executor utilities by EU_printf() in eutils.c |
|
128 | 94 | #undef EXEC_MERGEJOINDEBUG |
129 | 95 | */ |
130 | 96 |
|
131 | | -/* ---------------- |
132 | | - *EXEC_DEBUGINTERACTIVE is a flag which enables the |
133 | | - *user to issue "DEBUG" commands from an interactive |
134 | | - *backend. |
135 | | - * ---------------- |
136 | | -#undef EXEC_DEBUGINTERACTIVE |
137 | | - */ |
138 | | - |
139 | | -/* ---------------- |
140 | | - *EXEC_DEBUGVARIABLEFILE is string, which if defined will |
141 | | - *be loaded when the executor is initialized. If this |
142 | | - *string is not defined then nothing will be loaded.. |
143 | | - * |
144 | | - *Example: |
145 | | - * |
146 | | - * #define EXEC_DEBUGVARIABLEFILE "/a/postgres/cimarron/.pg_debugvars" |
147 | | - # |
148 | | - *Note: since these variables are read at execution time, |
149 | | - *they can't affect the first query.. this hack should be |
150 | | - *replaced by something better sometime. -cim 11/2/89 |
151 | | - * ---------------- |
152 | | -#undef EXEC_DEBUGVARIABLEFILE |
153 | | - */ |
154 | | - |
155 | 97 | /* ---------------------------------------------------------------- |
156 | 98 | *#defines controlled by above definitions |
157 | 99 | * |
|