Shouldn't GSSAPI and SSL code use FeBeWaitSet?

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Shouldn't GSSAPI and SSL code use FeBeWaitSet?
Дата
Msg-id CA+hUKGK=m9dLrq42oWQ4XfK9iDjGiZVwpQ1HkHrAPfG7Kh681g@mail.gmail.com
обсуждение исходный текст
Ответы Re: Shouldn't GSSAPI and SSL code use FeBeWaitSet?
Список pgsql-hackers
Hi,

While working on a patch to reuse a common WaitEventSet for latch
waits, I noticed that be-secure-gssapi.c and be-secure-openssl.c don't
use FeBeWaitSet.  They probably should, for consistency with
be-secure.c, because that surely holds the socket they want, no?  The
attached patch passes the "ssl" and "kerberos" tests and reaches that
code, confirmed by adding some log messages.

I'm not actually sure what the rationale is for reporting "terminating
connection due to unexpected postmaster exit" here but not elsewhere.
I copied the error from be-secure.c.

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Hubert Zhang
Дата:
Сообщение: Re: Yet another vectorized engine
Следующее
От: Thomas Munro
Дата:
Сообщение: Re: Shouldn't GSSAPI and SSL code use FeBeWaitSet?