[pgpool-general: 6548] Re: Almost there with pgpool, but it's not accepting all necessary connections
ishii at sraoss.co.jp
Tue May 7 11:15:17 JST 2019
> So, I've found another problem I think will fix most things now.
> I was using pg_md5 the same way to create both pgpool_passwd and the
> pcp.conf files,
> then I found out the method to create the hash for pcp.conf is different.
> If I make them this other way, which oddly (to me) puts the same hash in
> both the users I do this for (postgres and pgpool), it works for either
> user, if I -also- put the pcp.conf file in /etc/pgpool-II, as well as the
> pool_hba.conf in that directory.
> So, I had things created wrong and in some wrong places. Looks like what I
> need is this:
> pool_passwd is created in the same dir wherever I put pgpool.conf.
> pool_hba.conf and pcp.conf goes in /etc/pgpool-II, whether I like it or not.
You can specify the location of pool_hba.conf by using -a option of pgpool.
You can specify the location of pcp.conf by using -F option of pgpool.
See the documentation for more details.
> and the .pcppass file goes in the home directory of whatever user is
> running it (in this case postgres)
Yes, pgpool looks for the home directry which belongs to the user who
started pgpool by default. You can specify alternative path by using
PCPPASSFILE environment variable though.
SRA OSS, Inc. Japan
More information about the pgpool-general