Hello Jaume, thanks for answering. The pg_hba.conf contains this lines (on both db nodes): host all all 127.0.0.1/32 trust host all all 127.0.0.2/32 trust host all all 172.28.4.134/32 trust host all all 172.28.8.0/24 trust
Yes, it's not the safest setting, but for testing purpose enough. I try to connect from my workstation with IP 172.28.8.2. From my point of view it should work...?!?! If postgres forbids the connection shouldn't I see some log entries in postgresql.log ? regards...GERD... Jaume Sabater schrieb: > On Mon, Mar 16, 2009 at 2:08 PM, Gerd König <[email protected]> wrote: > >> O.K., normally I would say, I have to check >> pg_hba.conf/pool_hba.conf.....but: > > pg_hba.conf must exist and it refers to connections received by the > backends (from the IP address where pgpool-II is using to connect to > the backends). > > pool_hba.conf serves the same purpose but from the point of view of > pgpool-II, not PostgreSQL. And this is, of course, if it's enabled in > pgpool.conf. > -- /===============================\ | Gerd König | - Infrastruktur - | | TRANSPOREON GmbH | Pfarrer-Weiss-Weg 12 | DE - 89077 Ulm | | | Tel: +49 [0]731 16906 16 | Fax: +49 [0]731 16906 99 | Web: www.transporeon.com | \===============================/ Bleiben Sie auf dem Laufenden. Jetzt den Transporeon Newsletter abonnieren! http://www.transporeon.com/unternehmen_newsletter.shtml TRANSPOREON GmbH, Amtsgericht Ulm, HRB 722056 Geschäftsf.: Axel Busch, Peter Förster, Roland Hötzl, Marc-Oliver Simon _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
