Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitb810473

Browse files
committed
Don't VALGRIND_PRINTF() each query string.
Doing so was helpful for some Valgrind usage and distracting for otherusage. One can achieve the same effect by changing log_statement andpointing both PostgreSQL and Valgrind logging to stderr.Per gripe from Andres Freund.
1 parent277607d commitb810473

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

‎src/backend/tcop/postgres.c

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,6 @@
6969
#include"tcop/tcopprot.h"
7070
#include"tcop/utility.h"
7171
#include"utils/lsyscache.h"
72-
#include"utils/memdebug.h"
7372
#include"utils/memutils.h"
7473
#include"utils/ps_status.h"
7574
#include"utils/snapmgr.h"
@@ -847,10 +846,6 @@ exec_simple_query(const char *query_string)
847846

848847
TRACE_POSTGRESQL_QUERY_START(query_string);
849848

850-
#ifdefUSE_VALGRIND
851-
VALGRIND_PRINTF("statement: %s\n",query_string);
852-
#endif
853-
854849
/*
855850
* We use save_log_statement_stats so ShowUsage doesn't report incorrect
856851
* results because ResetUsage wasn't called.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp