diff options
author | Michael Paquier <michael@paquier.xyz> | 2023-06-23 17:50:23 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2023-06-23 17:50:23 +0900 |
commit | 4fd633df5080ef45b1a1665e6599463aad42305a (patch) | |
tree | facd5f9085960888229f34c66efce0f65c70d296 /src | |
parent | 8aac6140c8ac44fe34ad8242e37d8f94e0156c49 (diff) | |
download | postgresql-4fd633df5080ef45b1a1665e6599463aad42305a.tar.gz postgresql-4fd633df5080ef45b1a1665e6599463aad42305a.zip |
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
Diffstat (limited to 'src')
-rw-r--r-- | src/test/modules/libpq_pipeline/libpq_pipeline.c | 2 |
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 27332932a1e..b30a97d2817 100644 --- a/src/test/modules/libpq_pipeline/libpq_pipeline.c +++ b/src/test/modules/libpq_pipeline/libpq_pipeline.c @@ -961,7 +961,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))); |