summaryrefslogtreecommitdiff
path: root/contrib/test_decoding/test_decoding.c
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2025-09-30 23:52:28 +0900
committerFujii Masao <fujii@postgresql.org>2025-09-30 23:52:28 +0900
commit19d4f9ffc207c66b4755ffdf2dbd84b47e31460a (patch)
treebe488251d7434647757f25d4c0e325449f5fd211 /contrib/test_decoding/test_decoding.c
parent91df0465a69ddd249a548a63ee9d4aef6f984bf0 (diff)
pgbench: Fix error reporting in readCommandResponse().
pgbench uses readCommandResponse() to process server responses. When readCommandResponse() encounters an error during a call to PQgetResult() to fetch the current result, it attempts to report it with an additional error message from PQerrorMessage(). However, previously, this extra error message could be lost or become incorrect. The cause was that after fetching the current result (and detecting an error), readCommandResponse() called PQgetResult() again to peek at the next result. This second call could overwrite the libpq connection's error message before the original error was reported, causing the error message retrieved from PQerrorMessage() to be lost or overwritten. This commit fixes the issue by updating readCommandResponse() to use PQresultErrorMessage() instead of PQerrorMessage() to retrieve the error message generated when the PQgetResult() for the current result causes an error, ensuring the correct message is reported. Backpatch to all supported versions. Author: Yugo Nagata <nagata@sraoss.co.jp> Reviewed-by: Chao Li <lic@highgo.com> Reviewed-by: Fujii Masao <masao.fujii@gmail.com> Discussion: https://postgr.es/m/20250925110940.ebacc31725758ec47d5432c6@sraoss.co.jp Backpatch-through: 13
Diffstat (limited to 'contrib/test_decoding/test_decoding.c')
0 files changed, 0 insertions, 0 deletions