aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parser.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2023-04-03 10:18:38 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2023-04-03 10:18:38 -0400
commita8a00124f1ddb9c8506ff75317f6dd64cc480e61 (patch)
treed86a3e95b3a2dcb844e321e35faca958d7a433fa /src/backend/parser/parser.c
parentb0b91ced167f02ced4adaf1b2ecdc6fa0f6eb6e9 (diff)
downloadpostgresql-a8a00124f1ddb9c8506ff75317f6dd64cc480e61.tar.gz
postgresql-a8a00124f1ddb9c8506ff75317f6dd64cc480e61.zip
When using valgrind, log the current query after an error is detected.
In USE_VALGRIND builds, add code to print the text of the current query to the valgrind log whenever the valgrind error count has increased during the query. Valgrind will already have printed its report, if the error is distinct from ones already seen, so that this works out fairly well as a way of annotating the log. Onur Tirtir and Tom Lane Discussion: https://postgr.es/m/AM9PR83MB0498531E804DC8DF8CFF0E8FE9D09@AM9PR83MB0498.EURPRD83.prod.outlook.com
Diffstat (limited to 'src/backend/parser/parser.c')
0 files changed, 0 insertions, 0 deletions