View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000518 | Pgpool-II | General | public | 2019-05-23 02:10 | 2019-05-23 12:13 |
| Reporter | MaBikram | Assigned To | t-ishii | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Product Version | 4.0.5 | ||||
| Summary | 0000518: Questions on using connection pooling | ||||
| Description | Overview: We are running postgres 10.3 on centos 7, and we are trying to implement connection pooling using pgpool-II (ver 4.05). As we do not need replications yet, we installed pgpool on the postgres database server itself. We use pgpass file for connecting without password prompts. In using connection pooling, for connections' authentications, we are not using the pool_hba.conf ( enable_pool_hba = off in pgpool.conf). And, our pg_hba.conf has the following connection types: # TYPE DATABASE USER ADDRESS METHOD # "local" is for Unix domain socket connections only local all postgres peer local all all password # IPv4 local connections: host all all 127.0.0.1/32 password # IPv6 local connections: #host all all ::1/128 ident # Allow replication connections from localhost, by a user with the # replication privilege. local replication all host replication all 127.0.0.1/32 identl host replication all ::1/128 ident host all all 192.168.40.0/24 password Issue: We get errors in psql in using pgpool (see below): ============================================= -bash-4.2$ psql -p 9999 -U cemtore psql: FATAL: clear text password authentication failed DETAIL: unable to get the password for user: "cemtore" -bash-4.2$ psql -p 9999 -U cemtore Rb87#{ED09 psql: FATAL: clear text password authentication failed DETAIL: unable to get the password for user: "cemtore" -bash-4.2$ psql -p 9999 -U cemtore psql -p 9999 -U cemtore -h localhost psql: FATAL: clear text password authentication failed DETAIL: unable to get the password for user: "cemtore" -bash-4.2$ psql -p 9999 -U cemtore psql -p 9999 -U cemtore -h localhost -w psql: FATAL: clear text password authentication failed DETAIL: unable to get the password for user: "cemtore" Questions: ========= 1.Why pgpool connections can not use the pgpass password file ? If we change the IPv4 local connection method to trust then we do not get these errors. 2.We are using the default port 5432 for postgreSQL - but it seems for pgpool we need to use port 9999. What changes do we need in our applications to connect to database using pgpool ? | ||||
| Tags | No tags attached. | ||||
|
|
Firstly, this is not the best forum to ask questions (see our policy: https://pgpool.net/mediawiki/index.php/Bug_tracking_system). So please use mailing list for next time as suggested in the policy. > 1.Why pgpool connections can not use the pgpass password file? .pgpass is only useful for a user, while Pgpool-II needs to handle multiple users' passwords. If you don't want to create any password file for Pgpool-II, you could use "allow_clear_text_frontend_auth" feature. See http://www.pgpool.net/docs/latest/en/html/runtime-config-connection.html#RUNTIME-CONFIG-AUTHENTICATION-SETTINGS for more details. > 2.We are using the default port 5432 for postgreSQL - but it seems for pgpool we need to use port 9999. What changes do we need in our applications to connect to database using pgpool ? You can change 9999 to whatever port number you want to use by specifying "port" parameter. See http://www.pgpool.net/docs/latest/en/html/runtime-config-connection.html#RUNTIME-CONFIG-CONNECTION-SETTINGS |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-05-23 02:10 | MaBikram | New Issue | |
| 2019-05-23 09:27 | administrator | Assigned To | => t-ishii |
| 2019-05-23 09:27 | administrator | Status | new => assigned |
| 2019-05-23 12:12 | t-ishii | Note Added: 0002625 | |
| 2019-05-23 12:13 | t-ishii | Status | assigned => feedback |
