Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I think I have a compromise for --enable-debug: How about if
> --enable-debug removes optimization, adds -g (or -g3 for macro debugging
> symbols in gcc), and maybe even enables casserts.
This strikes me as a completely arbitrary set of changes in
long-established behavior. People who want to turn off optimization
already know how to do it, and people who want asserts already know
how to do that. Eliminating the functional difference between these
--enable options isn't a step forward.
regards, tom lane