Re: Why does WAL_DEBUG macro need to be defined by default?

Поиск
Список
Период
Сортировка
Искать
От
Kevin Grittner
Тема
Re: Why does WAL_DEBUG macro need to be defined by default?
Дата
Msg-id
4E8EEA800200002500041BA3@gw.wicourts.gov
Ответ на
Re: Why does WAL_DEBUG macro need to be defined by default? (Robert Haas)
Список
Дерево обсуждения
Why does WAL_DEBUG macro need to be defined by default? Fujii Masao <masao.fujii@gmail.com>
Re: Why does WAL_DEBUG macro need to be defined by default? Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Why does WAL_DEBUG macro need to be defined by default? Robert Haas <robertmhaas@gmail.com>
Re: Why does WAL_DEBUG macro need to be defined by default? "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Why does WAL_DEBUG macro need to be defined by default? Robert Haas <robertmhaas@gmail.com>
Re: Why does WAL_DEBUG macro need to be defined by default? Bruce Momjian <bruce@momjian.us>
Re: Why does WAL_DEBUG macro need to be defined by default? Robert Haas <robertmhaas@gmail.com>
Re: Why does WAL_DEBUG macro need to be defined by default? Bruce Momjian <bruce@momjian.us>
Re: Why does WAL_DEBUG macro need to be defined by default? Robert Haas <robertmhaas@gmail.com>
Re: Why does WAL_DEBUG macro need to be defined by default? Tom Lane <tgl@sss.pgh.pa.us> 
Robert Haas  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 по дате отправления
Предыдущее
От: Alex Hunsaker
Дата:
Следующее
От: Robert Haas
Дата:
FAQ