diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2022-08-15 15:40:07 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2022-08-15 15:40:07 -0400 |
commit | c19024d74e98e5c0ad95643ce584c52954d01b70 (patch) | |
tree | bd3fce98e5bf85e3999b353101aae3a56a88418d | |
parent | e2915afbd701e548d985ce8b834cbd13ff802ea1 (diff) | |
download | postgresql-c19024d74e98e5c0ad95643ce584c52954d01b70.tar.gz postgresql-c19024d74e98e5c0ad95643ce584c52954d01b70.zip |
Add missing bad-PGconn guards in libpq entry points.
There's a convention that externally-visible libpq functions should
check for a NULL PGconn pointer, and fail gracefully instead of
crashing. PQflush() and PQisnonblocking() didn't get that memo
though. Also add a similar check to PQdefaultSSLKeyPassHook_OpenSSL;
while it's not clear that ordinary usage could reach that with a
null conn pointer, it's cheap enough to check, so let's be consistent.
Daniele Varrazzo and Tom Lane
Discussion: https://postgr.es/m/CA+mi_8Zm_mVVyW1iNFgyMd9Oh0Nv8-F+7Y3-BqwMgTMHuo_h2Q@mail.gmail.com
-rw-r--r-- | src/interfaces/libpq/fe-exec.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/interfaces/libpq/fe-exec.c b/src/interfaces/libpq/fe-exec.c index b603ecfe7c7..ff101c4ca2a 100644 --- a/src/interfaces/libpq/fe-exec.c +++ b/src/interfaces/libpq/fe-exec.c @@ -3268,6 +3268,8 @@ PQsetnonblocking(PGconn *conn, int arg) int PQisnonblocking(const PGconn *conn) { + if (!conn || conn->status == CONNECTION_BAD) + return false; return pqIsnonblocking(conn); } @@ -3287,6 +3289,8 @@ PQisthreadsafe(void) int PQflush(PGconn *conn) { + if (!conn || conn->status == CONNECTION_BAD) + return -1; return pqFlush(conn); } |