TrojanWarBlade
Programmer
Guys,
We have pgpool configured to talk to two other servers each running postgres (8.3.8).
Each postgres system is configured to autovacuum (every 200 mins).
We create and drop many databases constantly.
It appears that sometimes autovacuum and our database creates occasionally clash when both need access to template1.
When this happens, as I understand it, pgpool drops the connection to the database in question.
The result is that subsequent inserts/updates are only being sent to one server and therefore our databases are getting out of sync very fast.
Are we doing something wrong here or is there some magic config that we need to know about to stop the server being dropped by pgpool?
Thanks
Trojan.
We have pgpool configured to talk to two other servers each running postgres (8.3.8).
Each postgres system is configured to autovacuum (every 200 mins).
We create and drop many databases constantly.
It appears that sometimes autovacuum and our database creates occasionally clash when both need access to template1.
When this happens, as I understand it, pgpool drops the connection to the database in question.
The result is that subsequent inserts/updates are only being sent to one server and therefore our databases are getting out of sync very fast.
Are we doing something wrong here or is there some magic config that we need to know about to stop the server being dropped by pgpool?
Thanks
Trojan.