summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane2016-10-10 14:35:58 +0000
committerTom Lane2016-10-10 14:35:58 +0000
commitfb6825fe57651dfd4dfe9d2041c715b03c5c6323 (patch)
treeae46f5b1c03062f1c748702051bf5c63f33eb8ac
parente84e4761f7ff83d657852d0d0a363868be715df2 (diff)
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>
-rw-r--r--src/interfaces/libpq/fe-exec.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/src/interfaces/libpq/fe-exec.c b/src/interfaces/libpq/fe-exec.c
index 68a848ab5bd..7418b152dc7 100644
--- a/src/interfaces/libpq/fe-exec.c
+++ b/src/interfaces/libpq/fe-exec.c
@@ -1240,8 +1240,7 @@ PQsendQueryStart(PGconn *conn)
}
/* initialize async result-accumulation state */
- conn->result = NULL;
- conn->curTuple = NULL;
+ pqClearAsyncResult(conn);
/* ready to send command message */
return true;