Add missing bad-PGconn guards in libpq entry points.
authorTom Lane <[email protected]>
Mon, 15 Aug 2022 19:40:07 +0000 (15:40 -0400)
committerTom Lane <[email protected]>
Mon, 15 Aug 2022 19:40:07 +0000 (15:40 -0400)
commit2a280832e1d0d79bfcaf7f394d9ead6880985032
treee01fe368aa007774ade69c8841629fc3800c0bad
parent1a05596eaaaaaa1e5596ef4c020a75ffaa762e32
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
src/interfaces/libpq/fe-exec.c