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. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
