postgres.git / summary / log / commit / refs

commit    f69a7f08fd01aa7d6dcd2c34dbdc4eb154a5ec12
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Fri Jun 23 08:49:07 2023 +0000
First released in: 16.0, 14.9, 15.4

    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


src/test/modules/libpq_pipeline/libpq_pipeline.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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))); [parent: c2122aae636d]