On Fri, Dec 4, 2015 at 7:45 AM, Pavel Stehule <pavel.steh...@gmail.com> wrote: > > > this tracing can be implemented to main pg_hba processing. When you are > connect from some specific client - and you can see, why you cannot to > connect to Postgres
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. Regards, Hari Babu Fujitsu Australia
hba_trace.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
