pgsql: Remove or reduce verbosity of some debug messages.

Поиск
Список
Период
Сортировка
От Robert Haas
Тема pgsql: Remove or reduce verbosity of some debug messages.
Дата
Msg-id E1c7Uwg-00055T-P4@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Remove or reduce verbosity of some debug messages.

The debug messages that merely print StartTransactionCommand,
CommitTransactionCommand, ProcessUtilty, or ProcessQuery with no
additional details seem to be useless.  Get rid of them.

The transaction status messages produced by ShowTransactionState are
occasionally useful, but they are extremely verbose, producing
multiple lines of log output every time they fire, which can happens
multiple times per transaction.  So, reduce the level to DEBUG5; avoid
emitting an extra line just to explain which debug point is at issue;
and tighten up the rest of the message so it doesn't use quite so much
horizontal space.

With these changes, it's possible to run a somewhat busy system with a
log level even as high as DEBUG4, whereas previously anything above
DEBUG2 would flood the log with output that probably wasn't really all
that useful.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/a43f1939d5dcd02f4df1604a68392332168e4be0

Modified Files
--------------
src/backend/access/transam/xact.c | 22 ++++++++++------------
src/backend/tcop/postgres.c       |  6 ------
src/backend/tcop/pquery.c         |  4 ----
3 files changed, 10 insertions(+), 22 deletions(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Fix pg_dump's handling of circular dependencies in views.
Следующее
От: Stephen Frost
Дата:
Сообщение: pgsql: Clean up pg_dump tests, re-enable BLOB testing