Both files include the same. pg_hba.conf ========= # "local" is for Unix domain socket connections only local all all trust# IPv4 local connections: host all all 127.0.0.1/32 trust host all all 192.168.158.38/32 trust host all all 192.168.158.39/32 trust # IPv6 local connections: host all all ::1/128 trust
pool_hba.conf ========== # "local" is for Unix domain socket connections only local all all trust # IPv4 local connections: host all all 127.0.0.1/32 trust host all all 192.168.158.38/32 trust host all all 192.168.158.39/32 trust Thanks, Nir On Mon, Nov 10, 2008 at 12:23 AM, Jaume Sabater <[EMAIL PROTECTED]>wrote: > nir osovsky wrote: > > > #enable_pool_hba = false enable_pool_hba = true > > As far as I know, if you turn this on you are telling pgpool-II to use > its own pg_hba.conf to do authentication of client connection attempts > (despite of the fact that PostgreSQL will do that again). Perhaps you > have not defined the custom pg_hba.conf of pgpool-II and therefore > pgpool-II cannot do the requested authentication? > > -- > Jaume Sabater > http://linuxsilo.net/ > > "Ubi sapientas ibi libertas" > > _______________________________________________ > Pgpool-general mailing list > [email protected] > http://pgfoundry.org/mailman/listinfo/pgpool-general >
_______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
