aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-10-10 10:35:58 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-10-10 10:35:58 -0400
commitbb211b66f2934fbfe85c091dbff8db9ac520ceb5 (patch)
treea06444faa74bba4ac42e986ca051b991372c7d4e /src
parentdca25c2562199ce1e7e26367613912a8eadbbde8 (diff)
downloadpostgresql-bb211b66f2934fbfe85c091dbff8db9ac520ceb5.tar.gz
postgresql-bb211b66f2934fbfe85c091dbff8db9ac520ceb5.zip
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>
Diffstat (limited to 'src')
-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 a9ba54628fd..87ff5659ff3 100644
--- a/src/interfaces/libpq/fe-exec.c
+++ b/src/interfaces/libpq/fe-exec.c
@@ -1386,8 +1386,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;