Postgres Pro
Downloads
Home   >   mailing lists

Re: Why does WAL_DEBUG macro need to be defined by default? - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Why does WAL_DEBUG macro need to be defined by default?
Date
Msg-id 4E8EEA800200002500041BA3@gw.wicourts.gov
Whole thread Raw
In response to Re: Why does WAL_DEBUG macro need to be defined by default?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Why does WAL_DEBUG macro need to be defined by default?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
Robert Haas <robertmhaas@gmail.com> wrote:
> The funny thing is that I've been thinking all of these months
> about how convenient it is that we defined WAL_DEBUG in debug
> builds
IMO, --enable-debug should not do anything but include debugging
symbols.  The ability to get a useful stack trace from a production
crash, without compromising performance, is just too important by
itself to consider conditioning any other behavior on it.
-Kevin

pgsql-hackers by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding.
Next
From: Robert Haas
Date:
Subject: Re: Why does WAL_DEBUG macro need to be defined by default?