Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit f69a7f0

Browse files
committed
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
1 parent c2122aa commit f69a7f0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/test/modules/libpq_pipeline/libpq_pipeline.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -959,7 +959,7 @@ test_prepared(PGconn *conn)
959959
pg_fatal("pipeline sync failed: %s", PQerrorMessage(conn));
960960
res = PQgetResult(conn);
961961
if (res == NULL)
962-
pg_fatal("expected NULL result");
962+
pg_fatal("PQgetResult returned null");
963963
if (PQresultStatus(res) != PGRES_COMMAND_OK)
964964
pg_fatal("expected COMMAND_OK, got %s", PQresStatus(PQresultStatus(res)));
965965

0 commit comments

Comments
 (0)