Hello, today I got back to this issue and, please, forgive me :-)) It was the "don't see the forest but the trees"-problem. After installing pgpool from scratch I forgot to set the parameter "listen_addresses", thereby it was set to 'localhost' by default.
silly me...............GERD.............. Jaume Sabater schrieb: > 2009/3/16 Gerd König <[email protected]>: > > >> host all all 172.28.4.134/32 trust > > I'll take this is the local IP address that both PostgreSQL and > pgpool-II listen at. If so, I think that it should work. > >> If postgres forbids the connection shouldn't I see some log entries in >> postgresql.log ? > > I cannot remember, but I think so. Try setting log_connections=on and > log_statements='all' in postgresql.conf and restart PostgreSQL. > -- /===============================\ | 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
