Re: TRACE_SORT defined by default
| От | Tom Lane |
|---|---|
| Тема | Re: TRACE_SORT defined by default |
| Дата | |
| Msg-id | 31375.1556225793@sss.pgh.pa.us обсуждение |
| Ответ на | Re: TRACE_SORT defined by default (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Ответы |
Re: TRACE_SORT defined by default
|
| Список | pgsql-hackers |
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2019-Apr-25, Jeff Janes wrote:
>> I've had people use it to get some insight into the operation and memory
>> usage of Aggregate nodes, since those nodes offer nothing useful via
>> EXPLAIN ANALYZE. It would be a shame to lose that ability on
>> package-installed PostgreSQL unless we fix Aggregate node reporting first.
> But the proposal is not to remove the _code_. The proposal is just to
> remove that "#ifdef" lines that would make it conditionally compilable,
> *if* the symbol that they test weren't always enabled. In other words,
> turn it from "always compiled, but you can turn it off although nobody
> does" into "always compiled".
Well, I was suggesting that we ought to consider the alternative of
making it *not* always compiled, and Jeff was pushing back on that.
regards, tom lane
В списке pgsql-hackers по дате отправления: