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_...@mail.gmail.com Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/e37e9a65517552e79614a1c81c8aff216d033e59 Modified Files -------------- src/interfaces/libpq/fe-exec.c | 4 ++++ src/interfaces/libpq/fe-secure-openssl.c | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-)
