Commit4fd633d

committed

Fix incorrect error message in libpq_pipeline

One of the tests for the pipeline mode with portal description expects anon-NULL PQgetResult, but used an incorrect error message on failure,telling that PQgetResult being NULL was the expected result.Author: Jelte FennemaDiscussion:https://postgr.es/m/CAGECzQTkShHecFF+EZrm94Lbsu2ej569T=bz+PjMbw9Aiioxuw@mail.gmail.comBackpatch-through: 14

1 parent8aac614 commit4fd633dCopy full SHA for 4fd633d

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -961,7 +961,7 @@ test_prepared(PGconn *conn)`
`961`	`961`	`pg_fatal("pipeline sync failed: %s",PQerrorMessage(conn));`
`962`	`962`	`res=PQgetResult(conn);`
`963`	`963`	`if (res==NULL)`
`964`		`-pg_fatal("expected NULL result");`
	`964`	`+pg_fatal("PQgetResult returned null");`
`965`	`965`	`if (PQresultStatus(res)!=PGRES_COMMAND_OK)`
`966`	`966`	`pg_fatal("expected COMMAND_OK, got %s",PQresStatus(PQresultStatus(res)));`
`967`	`967`

Comments

(0)