summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier2023-06-23 08:49:07 +0000
committerMichael Paquier2023-06-23 08:49:07 +0000
commitf69a7f08fd01aa7d6dcd2c34dbdc4eb154a5ec12 (patch)
treedcff6936ecdcc2ce217cb6f4e6f860d15144f8c9
parentc2122aae636d7121d5cdb64ad1444e1df7f69257 (diff)
Fix incorrect error message in libpq_pipeline
One of the tests for the pipeline mode with portal description expects a non-NULL PQgetResult, but used an incorrect error message on failure, telling that PQgetResult being NULL was the expected result. Author: Jelte Fennema Discussion: https://postgr.es/m/CAGECzQTkShHecFF+EZrm94Lbsu2ej569T=bz+PjMbw9Aiioxuw@mail.gmail.com Backpatch-through: 14
-rw-r--r--src/test/modules/libpq_pipeline/libpq_pipeline.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/modules/libpq_pipeline/libpq_pipeline.c b/src/test/modules/libpq_pipeline/libpq_pipeline.c
index f5b4d4d1ff2..1933b078ebf 100644
--- a/src/test/modules/libpq_pipeline/libpq_pipeline.c
+++ b/src/test/modules/libpq_pipeline/libpq_pipeline.c
@@ -959,7 +959,7 @@ test_prepared(PGconn *conn)
pg_fatal("pipeline sync failed: %s", PQerrorMessage(conn));
res = PQgetResult(conn);
if (res == NULL)
- pg_fatal("expected NULL result");
+ pg_fatal("PQgetResult returned null");
if (PQresultStatus(res) != PGRES_COMMAND_OK)
pg_fatal("expected COMMAND_OK, got %s", PQresStatus(PQresultStatus(res)));