Hi,
fortunately the problems with a malfunctioning client during
the authentication don't cause the v7.2 postmaster to hang
any more (thanks to Peter and Tom). The client authentication
is moved into the forked off process.
Now one little problem remains. If a bogus client causes a
child to hang before becoming a real backend, this child is
in the backend list of the postmaster, but has all signals
blocked. Thus, preventing the postmaster from beeing able to
shutdown.
I think the correct behaviour should be to enable SIGTERM and
SIGQUIT during client authentication and simply exit(0) if
they occur. If so, what would be the best way to get these
two signals out of the block mask?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== [EMAIL PROTECTED] #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
