Re: TRACE_SORT defined by default - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: TRACE_SORT defined by default
Date
Msg-id 20190425205203.GA11285@alvherre.pgsql
Whole thread Raw
In response to Re: TRACE_SORT defined by default  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: TRACE_SORT defined by default
Re: TRACE_SORT defined by default
List pgsql-hackers
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".

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: "Routine Reindexing" docs should be updated to reference REINDEX CONCURRENTLY
Next
From: Peter Geoghegan
Date:
Subject: Re: TRACE_SORT defined by default