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
commit886f6c5ccdb500eeeec7e0abdf1500e20a304c45 (patch)
tree6ef81618e029ddc4f4872604e656248686f8392d /src
parent6fb12cbcd6f1a971e113d7d32cc7ee920db4e097 (diff)
downloadpostgresql-886f6c5ccdb500eeeec7e0abdf1500e20a304c45.tar.gz
postgresql-886f6c5ccdb500eeeec7e0abdf1500e20a304c45.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;