From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_hba_lookup function to get all matching pg_hba.conf entries |
Date: | 2015-12-04 06:21:47 |
Message-ID: | CAFj8pRBUUZfaRVeVVoJiFGHKh-_Q1h-apH+n14wx7kK4ov8AWQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2015-12-04 5:48 GMT+01:00 Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>:
> On Fri, Dec 4, 2015 at 7:45 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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?
>
yes, it is only for admin and should be stored to log
>
> [kommih(at)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-12-04 06:23:45 | Re: psql --help=variables lists variables that can't be set |
Previous Message | Pavel Stehule | 2015-12-04 06:20:45 | Re: pg_hba_lookup function to get all matching pg_hba.conf entries |