From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon, 10 Oct 2016 14:35:58 +0000 (-0400)
Subject: In PQsendQueryStart(), avoid leaking any left-over async result.
X-Git-Tag: REL9_2_19~17
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7397f62e7fd9a90bba8c8dc8d61c569a41040762;p=postgresql

In PQsendQueryStart(), avoid leaking any left-over async result.

Ordinarily there would not be an async result sitting around at this
point, but it appears that in corner cases there can be.  Considering
all the work we're about to launch, it's hardly going to cost anything
noticeable to check.

It's been like this forever, so back-patch to all supported branches.

Report: <CAD-Qf1eLUtBOTPXyFQGW-4eEsop31tVVdZPu4kL9pbQ6tJPO8g@mail.gmail.com>
---

diff --git a/src/interfaces/libpq/fe-exec.c b/src/interfaces/libpq/fe-exec.c
index c2ab2ce2f5..6e0dcb62e7 100644
--- a/src/interfaces/libpq/fe-exec.c
+++ b/src/interfaces/libpq/fe-exec.c
@@ -1362,8 +1362,7 @@ PQsendQueryStart(PGconn *conn)
 	}
 
 	/* initialize async result-accumulation state */
-	conn->result = NULL;
-	conn->next_result = NULL;
+	pqClearAsyncResult(conn);
 
 	/* reset single-row processing mode */
 	conn->singleRowMode = false;