Re: pg_hba_lookup function to get all matching pg_hba.conf entries
От | Pavel Stehule |
---|---|
Тема | Re: pg_hba_lookup function to get all matching pg_hba.conf entries |
Дата | |
Msg-id | CAFj8pRDrrn0xDd9e5+JFPNWH8L2O6C+_L7Ab0MP_3aTcN4vUxg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_hba_lookup function to get all matching pg_hba.conf entries (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: pg_hba_lookup function to get all matching pg_hba.conf
entries
|
Список | pgsql-hackers |
2015-12-04 17:16 GMT+01:00 Alvaro Herrera <alvherre@2ndquadrant.com>:
Haribabu Kommi wrote:
> The trace messages that are going to print doesn't come to client until the
> connection gets successful. The traces may not useful for the clients
> to find out
> why the connection is failing. But it may be useful for administrators.
> How about the attached patch?
>
> [kommih@localhost bin]$ ./psql postgres -h ::1
> psql (9.6devel)
> Type "help" for help.
>
> postgres=#
>
> ServerLog:
> NOTICE: Skipped 84 pg_hba line, because of host connection type.
> NOTICE: Skipped 86 pg_hba line, because of non matching IP.
That's going to be way too noisy. Some applications open dozens of
connections per second -- imagine a dozen NOTICEs per each connection
established. It's going to fill any disk you install as the server log
partition ...
I can imagine worse nightmares, but this one's a pretty ugly one.
It should be disabled by default
only when you have some problems, then you can enable it
Regards
Pavel
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: