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>
This commit is contained in:
parent
e84e4761f7
commit
fb6825fe57
|
@ -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;
|
||||
|
|
Loading…
Reference in New Issue