From cb10504f09f767d6bfb12a2d7ca55ac31393f3ad Mon Sep 17 00:00:00 2001
From: Jelte Fennema <jelte.fennema@microsoft.com>
Date: Fri, 23 Jun 2023 09:02:11 +0200
Subject: [PATCH v6 1/2] Correct error message in test_prepared

It said it expecting a NULL result, but it was actually expecting the
opposite. This probably originated from a copy-paste mistake.
---
 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)));
 

base-commit: c2122aae636d7121d5cdb64ad1444e1df7f69257
-- 
2.34.1

