Fix pg_pwd caching mechanism, which was broken by changes to fork
postmaster children before client auth step. Postmaster now rereads pg_pwd on receipt of SIGHUP, the same way that pg_hba.conf is handled. No cycles need be expended to validate password cache validity during connection startup.
Showing
- doc/src/sgml/client-auth.sgml 54 additions, 14 deletionsdoc/src/sgml/client-auth.sgml
- doc/src/sgml/runtime.sgml 5 additions, 3 deletionsdoc/src/sgml/runtime.sgml
- src/backend/commands/user.c 10 additions, 17 deletionssrc/backend/commands/user.c
- src/backend/libpq/crypt.c 93 additions, 91 deletionssrc/backend/libpq/crypt.c
- src/backend/postmaster/postmaster.c 8 additions, 3 deletionssrc/backend/postmaster/postmaster.c
- src/include/libpq/crypt.h 13 additions, 14 deletionssrc/include/libpq/crypt.h
Loading
Please register or sign in to comment