diff options
| author | Michael Paquier <michael@paquier.xyz> | 2023-06-23 17:50:28 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2023-06-23 17:50:28 +0900 |
| commit | 451ca5c1e699c4448875fc12d9ed6d84a2e7816d (patch) | |
| tree | bd649d87813c61a0bc3a76f0aa201e49cbd1a83b | |
| parent | 991983fcf650a5cecaefff5dc10a55ff865f57cb (diff) | |
| download | postgresql-451ca5c1e699c4448875fc12d9ed6d84a2e7816d.tar.gz postgresql-451ca5c1e699c4448875fc12d9ed6d84a2e7816d.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
| -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 95e653c8c3b..b6f5fd28b23 100644 --- a/src/test/modules/libpq_pipeline/libpq_pipeline.c +++ b/src/test/modules/libpq_pipeline/libpq_pipeline.c @@ -949,7 +949,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))); |