16 July 2018
(This is another intermittent series of small things that are easy to forget, and cause irritation in the PostgreSQL world…)
When setting up
pgpool2, it’s common to tweak the configuration file repeatedly… and often get a hostname wrong. One common occurrence is then:
- You fix the hostnames.
- You restart pgpool2.
- It refuses to connect to the host you just fixed.
- You scratch your head, connect manually with
psql, everything works…
- But pgpool2 just will not acknowledge that host.
Often, the problem is that the
pgpool_status file, usually kept in
/tmp, has cached the status of one of the hosts. The
pgpool_status file is retained across
pgpool2 restarts. Deleting the
pgpool_status file will fix the issue.
(Why, yes, this just happened to me today…)