diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-07-13 11:57:55 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-07-13 11:58:08 -0400 |
| commit | 25fe5ac45a736e50d2b85280a3cb0ce169f583f3 (patch) | |
| tree | 6fe5cd497b9b9cf7dc65d38ae80f82b23ec7451c /src/backend/access/transam/xlog.c | |
| parent | 8d2ed66e4107ef27d05aef682c68af5952af7690 (diff) | |
| download | postgresql-25fe5ac45a736e50d2b85280a3cb0ce169f583f3.tar.gz postgresql-25fe5ac45a736e50d2b85280a3cb0ce169f583f3.zip | |
Fix bugs in libpq's management of GSS encryption state.
GSS-related resources should be cleaned up in pqDropConnection,
not freePGconn, else the wrong things happen when resetting
a connection or trying to switch to a different server.
It's also critical to reset conn->gssenc there.
During connection setup, initialize conn->try_gss at the correct
place, else switching to a different server won't work right.
Remove now-redundant cleanup of GSS resources around one (and, for
some reason, only one) pqDropConnection call in connectDBStart.
Per report from Kyotaro Horiguchi that psql would freeze up,
rather than successfully resetting a GSS-encrypted connection
after a server restart.
This is YA oversight in commit b0b39f72b, so back-patch to v12.
Discussion: https://postgr.es/m/20200710.173803.435804731896516388.horikyota.ntt@gmail.com
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions